Saravanan666/pypi-org huggingface dataset:
Package: appenlight-diamond
# appenlight_diamond
Python-Diamond handler for App EnlightUsageIf not using diamond version that comes with bundled handler,
you first need to install the package:pip install appenlight_diamondThen you need to add the handler to yourdiamond.confhandler section:# Handlers for published metrics.
handlers = diamond.handler.appenlight.AppenlightMetricHandler, ..., diamond.handler.archive.ArchiveHandlerIf your installation doesn’t ship the handler yet the handler and you installed it
on your own, line needs to be slightly different:# Handlers for published metrics.
handlers = appenlight_diamond.AppenlightMetricHandler, ..., diamond.handler.archive.ArchiveHandlerFinally, you need to add a configuration section:[[AppenlightMetricHandler]]
apikey = PRIVATE_API_KEY
#server =http://optional.custom.server.comapikeyis mandatory,serveris optional and by defaulthttps://api.appenlight.comwill be used as default value.
Package: appenv
through shared repositories.
Home-page:https://github.com/flyingcircusio/appenv/Author: Christian Theune
Author-email:ct@flyingcircus.ioLicense: BSD (3-clause)
Description: UNKNOWN
Keywords: deployment
Platform: UNKNOWN
Classifier: License :: OSI Approved :: BSD License
Classifier: Programming Language :: Python
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.6
Classifier: Programming Language :: Python :: 3.7
Classifier: Programming Language :: Python :: 3.8
Classifier: Programming Language :: Python :: 3 :: Only
Requires-Python: >=3.6
Package: appermissions
A sample project that exists as an aid to the [Python Packaging UserGuide][packaging guide]'s [Tutorial on Packaging and DistributingProjects][distribution tutorial].This project does not aim to cover best practices for Python projectdevelopment as a whole. For example, it does not provide guidance or toolrecommendations for version control, documentation, or testing.[The source for this project is available here][src].Most of the configuration for a Python project is done in the `setup.py` file,an example of which is included in this project. You should edit this fileaccordingly to adapt this sample project to your needs.----This is the README file for the project.The file should use UTF-8 encoding and can be written using[reStructuredText][rst] or [markdown][md use] with the appropriate [key set][mduse]. It will be used to generate the project webpage on PyPI and will bedisplayed as the project homepage on common code-hosting services, and should bewritten for that purpose.Typical contents for this file would include an overview of the project, basicusage examples, etc. Generally, including the project changelog in here is not agood idea, although a simple “What's New” section for the most recent versionmay be appropriate.[packaging guide]: https://packaging.python.org[distribution tutorial]: https://packaging.python.org/en/latest/distributing.html[src]: https://github.com/pypa/sampleproject[rst]: http://docutils.sourceforge.net/rst.html[md]: https://tools.ietf.org/html/rfc7764#section-3.5 "CommonMark variant"[md use]: https://packaging.python.org/specifications/core-metadata/#description-content-type-optionalKeywords: application permissions setuptools developmentPlatform: UNKNOWNClassifier: Development Status :: 3 - Production/StableClassifier: Intended Audience :: DevelopersClassifier: Topic :: Software Development :: Build ToolsClassifier: License :: OSI Approved :: MIT LicenseClassifier: Programming Language :: Python :: 3Classifier: Programming Language :: Python :: 3.4Classifier: Programming Language :: Python :: 3.5Classifier: Programming Language :: Python :: 3.6
Package: appeus.content
IntroductionThis product may contain traces of nuts.Changelog1.0 (2015-02-19)add manifest [Mikel Larreategi <mlarreategi@codesyntax.com>]remove zopeskel [Mikel Larreategi <mlarreategi@codesyntax.com>]template details [Mikel Larreategi <mlarreategi@codesyntax.com>]layout [Mikel Larreategi <mlarreategi@codesyntax.com>]dependencies [Mikel Larreategi <mlarreategi@codesyntax.com>]vocabulary for apps [Mikel Larreategi <mlarreategi@codesyntax.com>]register indexer for boolean fields [Mikel Larreategi <mlarreategi@codesyntax.com>]translation [Mikel Larreategi <mlarreategi@codesyntax.com>]translations [Mikel Larreategi <mlarreategi@codesyntax.com>]change template [Mikel Larreategi <mlarreategi@codesyntax.com>]if price=true show price [Mikel Larreategi <mlarreategi@codesyntax.com>]changes in fields [Mikel Larreategi <mlarreategi@codesyntax.com>]faceted view [Mikel Larreategi <mlarreategi@codesyntax.com>]view [Mikel Larreategi <mlarreategi@codesyntax.com>]import from itunes [Mikel Larreategi <mlarreategi@codesyntax.com>]Google play import [Mikel Larreategi <mlarreategi@codesyntax.com>]initial implementation [Mikel Larreategi <mlarreategi@codesyntax.com>]
Package: app-executor
app_executorThis program might be used for launching external executables from python script.
It can also collectstdoutandstderrof them and store it into text file.
In case of any failure it can also provide some basic stacktrace collection.Importingapp_executorpackage gives an access to two essential classes:app_executor.Process- this class can be used for direct launching processesapp_executor.AppExecutor- this class can be used for automatic managing of
launching multiple processesExample usageapp_executor.ProcessThis code launcheswhoamiand aliases it asMyName- all warning/error prints
will be having this alias for increasing readability. Then it runs the process
and waits up to 1 second for it to finish. In the end it prints result code and
actual output (stdout and stderr combined) of executed command.In the exit step command will be stopped (firstlyapp_executor.Processwill try
to terminate it and if that fails - kill it). And afterwards it will perform
core dump analysis (if core dump was collected during the execution).All result files - logs fromgdb, process itself, core dump and stacktrace will
be put into/some/path/MyNamedirectory.importapp_executorwithapp_executor.Process(name='MyName',cmd='whoami',parent_context_dir='/some/path')asprocess:process.run()ifnotprocess.wait(timeout=1):raiseException('Process hanged for too long!')print('Returncode was:{}'.format(process.get_rc()))print('Output of whoami:{}'.format(process.get_logfile()))app_executor.AppExecutorThis code works similar to former. Here execution path is passed once for all
processes launched later on.app_executor.AppExecutorcan either assign
aliases by itself (process_1,process_2, etc.) or user can set them manually.runfunction returnsapp_executor.Processobject that can be used to interact
with the process later on (similarly as in former example).In the exit stepapp_executor.AppExecutorwill stop every child process and
perform dump analysis if core dump were collected. All result files will be stored
under the path/some/path/$NAME_OF_THE_PROCESS.importapp_executorwithapp_executor.AppExecutor('/some/path')asexecutor:p1=executor.run('whoami')p2=executor.run('sleep 1','MyCustomAlias')# ...# operations on p1 and p2 app_executor.Process objects# ...executorfixtureTogether with installingapp_executorpackageexecutorpytest fixture becomes
available. It createsapp_executor.AppExecutorand passestmpdiras work
directory to it. On fixture teardown all spawned processes are stopped.deftest_some_executing(executor):p1=executor.run('whoami')p2=executor.run('sleep 1')# ...# operations on p1 and p2 app_executor.Process objects# ...
Package: appfire-connect-sdk
Appfire connect app SDKWhat does it do?Creates a Atlassian Connect app template and provides a toolkit for deploying to AWS environmentCommand Line Arguments--verbose, -v : "verbose"
--region, -r : "AWS region", default="us-east-1"
--profile, -p : "AWS profile as the default environment", default="default"
--env, -e : "personal, dev, test, stage or prod", default="personal"
--stack, -s : "CDK stack to deploy", default="app", "core" or "app"
--stage, -stage : "dev, test, stage or prod", default="dev"
--app-suffix, -as : "green" or nothing (not passing the argument)Note: see personal.env.yml or env.yml for personal or DTS/Prod environments respectively.Run via Pythoncreate-appfire-app -vBootstrap appbootstraps CDK toolkitappfire bootstrapDeploy core stackappfire deploy -s coreDeploy biz service stackappfire deploy -s biz-serviceDeploy app service stackappfire deploy -s app-serviceDeploy module service stackappfire deploy -s module-serviceDeploy appappfire deployList stacksappfire list (or appfire ls)Diff stackappfire diffDestroy app stackappfire destroyRun the appThe app will run locally on port 9000 using the AWS_PROFILE as set from personal.env.yaml ['environment']['personal']['profile']appfire runBuild and Run SDK locallypython setup.py build && python setup.py installPossible IssuesIf you are gettingSSL: CERTIFICATE_VERIFY_FAILEDwhile running install command, run following file/Applications/Python 3X/Install Certificates.command
Package: appflow-patterns
Appflow Patterns - a library to facilitate data flowsThis library aims at simplifying the task of setting up data flows between SaaS like SharePoint and S3.This library is  written using the wonderfulprojenframework.Note: this library is just the result of some personal experimentation. It is not an official AWS library and is not supported by AWS!InstallationThe library is available on npmjs.com and can be installed using:npm i dms-patternsAnd on pypi:pip install dms-patternsUsage ExamplesSharepoint to S3This example creates a scheduled and ondemand flow from a sharepoint site to an s3 bucket.import{Sharepoint2S3Flow}from'../src/appflow-patterns/sharepoint2s3';exportclassSharepoint2S3Stackextendscdk.Stack{constructor(scope:Construct,id:string,props:cdk.StackProps){super(scope,id,props);constbucket=news3.Bucket(this,'Bucket',{bucketName:'my-bucket',});newSharepoint2S3Flow(this,'Sharepoint2S3Flow',{site:'sites/${siteName},${siteID},${webID}',entities:['${site}/_api/v2.0/drive/root:/path/to/folder'],profileArn:'arn:aws:appflow:us-east-1:123456789012:connector-profile/12345678-1234-1234-1234-123456789012',bucketName:bucket.bucketName,scheduleExpression:'rate(12 hour)',});}}Currently, only carbon-based entities are supported due to a limitation of AWS Appflow.
Package: appframe
Introduction and InstallationAppframe is an open source python library that reduces the code and complexity of developing command line applications. It handles most of the low level logic while enforcing a modular architecture.Features2 lines of code for themainfunctionComposition of the CLI commands from acommands/directoryAppframe leverages the follwing greate libraries:https://pypi.org/project/cleo/https://pypi.org/project/simple-plugin-loader/InstallationAppframe is avaiable from the official Python Package Index (PIP), you can install it from the terminal:pipinstallappframeHello Worldmain.pyimportappframeappframe.main(__name__,__file__,"test-app","0.1")commands/hello.pyfromappframeimportCommand,verboseclassCreateCommand(Command):"""Greet a persongreet{person? : name of the person to greet}"""defhandle(self):person=self.argument("person")or"Peter"verbose(1,"Greeting person")print(f"Hello{person}")Test the app:pythontest.pygreetJoe
Package: app-global
app_globalFromdocs.python.org:"The canonical way to share information across modules within a single program is to create a special module (often called config or cfg). Just import the config module in all modules of your application; the module then becomes available as a global name. Because there is only one instance of each module, any changes made to the module object get reflected everywhere. For example:"See /Example/app_global_test for an illustration that can be run in VSCodeAlthough not illustrated, it is recommended to categorize data within the app globals to keep organized and thus reduce possiblity obscure failure:config.C - For global constantsconfig.G - For global application state like DB connections, caches etc.config.opts - Application optionsconfig.log - Application loggerconfig.printCli - Common print cli handler for clean exit during initializationAs with any global data, care should be taken when using from within any multi threading applications. Use appropriate locking mechanisms as required.Besides improving documentation, the main sourceconfig.pywill be left as an empty source file so that is infinitely flexible
Package: app-graphs
app-graphsOriginal repository(github).PyPI.app-graphsusesogdf-pythonwhich in turn usesOGDF.
app-graphs draws a graph from data given in .xlsx format. Nodes are generated from given aplications and components as well as from interfaces, where interface represents node and two edges conected to it and source/target node. Edges are generated between aplication and its components and from directed edges provided.InstallationFirst we need to installOGDF. This is done by downloading OGDF, unziping it and calling following commands in bash:foo@bar:~ogdf$mkdirogdf-debugogdf-release
foo@bar:~ogdf$cdogdf-debug
foo@bar:~ogdf/ogdf-debug$cmake..
foo@bar:~ogdf/ogdf-debug$ccmake..Configure BUILD_SHARED_LIB=ON and CMAKE_BUILD_TYPE=Debug when calling last line.foo@bar:~ogdf/ogdf-debug$makeRepeat above for release (debug <-> release). And as a last step add ogdf to path.foo@bar:~ogdf$exportOGDF_BUILD_DIR=~/ogdf/ogdf-debugAs a last step install app-graphs.pipinstallapp-graphsUsagefromapp_graphsimportgraph# Define graph instancemy_graph=graph()# Read data from filename_aplikacije and vmesniki_sheet_namemy_graph.read(filename_apps=r'example.xlsx',# name of file containing information about apps and componentsapps_sheet_name='Aplication list',# name of sheet in above filefilename_interfaces=r'example.xlsx',# name of file containing information about interfacesinterfaces_sheet_name='Integration list',# name of sheet in above fileapps='Aplications',# name of apps names columncomponents='Components',# name of components names columnsource='Source',# name of interface's source app/component columntarget='Target',# name of interface's target app/component columninterface_direction='Direction',# name of interface direction columntechnologies='Technology',# name of technologies names columncolors='Colors'# name of colors column)# Uses ogdf-python to generate graphmy_graph.draw()# Saves genereted graph in desired formatmy_graph.save_svg('test-graph')
Package: apphb
Python Application HeartbeatsA Python application-level heartbeats interface.InstallingTheapphbpackage is published in the Python Package Index and installable with pip:pipinstallapphband through Conda Forge:condainstallenergymonTo install from source:pipinstall.UsageThe core component is theHeartbeatclass.
The user defines a window period (window_size) that specifies a sliding window length over which performance is computed.
Users may optionally specify other fields to compute sums and rates for.For example:total_iters=10window_size=2hbt=Heartbeat(window_size)fortaginrange(total_iters):start_time=time.monotonic()application_kernel()end_time=time.monotonic()hbt.heartbeat(tag,(end_time-start_time,))print(str(tag)+': Instant performance: '+str(hbt.get_instant_rate()))print(str(tag)+': Window performance: '+str(hbt.get_window_rate()))print('Global performance: '+str(hbt.get_global_rate()))See theexamplesdirectory for more detailed use cases, including specifying custom fields.Project SourceFind this and related project sources at thelibheartbeats organization on GitHub.This project originates at:https://github.com/libheartbeats/apphb-pythonBug reports and pull requests for bug fixes and enhancements are welcome.
Package: apphelpers
Common helper libraries for Python AppsCommon helper libraries for Python AppsFree software: MIT licenseDocumentation:https://apphelpers.readthedocs.io.FeaturesTODOCreditsThis package was created withCookiecutterand theaudreyr/cookiecutter-pypackageproject template.History0.93.1 (2023-01-20)Fixed get_by_secondary_key of CachedModel0.93.0 (2023-01-19)Added secondary_key support for CachedModel0.92.3 (2023-01-15)Added @response_model for FastAPI endpoints0.92.2 (2023-12-26)Fixed operation_id generation0.92.1 (2023-12-24)Fixed _get_matched_keys access for ReadOnlyCachedModel0.92.0 (2023-12-23)site_ctx implementation for FastAPIuser_agent directive for FastAPI & Hugignore_site_ctx implementation for FastAPI & Hugcount_matched_keys implementation for ReadOnlyCachedModel0.91.0 (2023-12-22)Breaking: moved apphelpers.sessions.whoami to apphelpers.rest.{hug/fastapi}.whoamiNew convenient decorators in apphelpers.rest.endpointany_group_required and all_groups_required implementation for FastAPIImproved errorsOther improvements and fixesMoved CI from travis to github actions0.90.0 (2023-10-16)Support for FastAPI framework.0.34.2 (2023-09-04)Email INTERNAL_EMAIL_DOMAINS will also restrict bcc email recipients.Fixed typo0.34.0 (2023-09-01)settings.INTERNAL_EMAIL_DOMAINS must me defined for email sending safety in
non-prod env.
e.g. INTERNAL_EMAIL_DOMAINS = [‘example.com’, ‘example.org’]
allows sending emails to only address ending with example.com or example.org0.33.5 (2023-08-08)Reusable utilityformat_msgadded in email module to format email message0.33.4 (2023-08-08)Support for optionally addding headers added to email message0.33.3 (2023-08-04)For site-bound sessions, restrict access if site_id is missing0.33.2 (2023-07-20)session destroy fix for site-bound sessions0.33.1 (2023-07-20)site_id check fix for site-bound sessions0.33.0 (2023-05-23)Support for new directives: user_groups, user_site_groups, user_site_ctxAmbiguously named groups_required decorator is now replaced with any_group_requiredNew decorator: all_groups_required0.32.1 (2023-04-18)Support for resyncing & destroying context bound session0.32.0 (2023-04-11)Support for context bound sessions0.31.2 (2022-12-15)Implement ReadWriteCachedModel.decrement()0.31.1 (2022-09-20)Extend sesion timeout fix for lookup keyImplement sessions.sid2uid()0.31.0 (2022-08-08)Rename Config directive MD_* to SMTP_*0.21.1 (2022-06-09)Fix for SMTP+SSL connection0.21.0 (2022-05-18)applogger: general purpose application logging0.20.0 (2022-04-29)Support for custom authorizaion0.19.1 (2021-10-07)Report function args in honeybadger context0.9.2 (2019-05-20)New optionsgroups_forbiddenandgroups_requiredto secure API access0.1.0 (2019-03-24)First release on PyPI.
Package: apphub
PyAppHubPython package for Swimlane AppHub APIInstallrunpip install apphubfrom a terminal. This package is available for python 3.6 or greater.ExamplesBelow are a few basic python examples to get started.Note: Ifsw_is not found at the beginning of a name, the client will
add it for you.fromapphubimportAppHub,save_to_disk,clean_responseah=AppHub('username','password')# Get all swimlane bundlesget_all_bundles=ah.swimbundles.get()# Get All versions of a swimlane bundleget_all_versions=ah.swimbundles.get('sw_elastic_kibana')# Get One version of a swimlane bundleget_one_version=ah.swimbundles.get('sw_elastic_kibana','2.0.0')ah.swimbundles.search(text="elastic")# Download bundle by versiondownloaded_bundle=ah.swimbundles.download('sw_elastic_kibana','2.0.0')clean_response(get_all_bundles)srch_by_field=ah.swimbundles.search(fields={'vendor':"Elastic"})srch_by_text=ah.swimbundles.search(text="Elastic")# Save Latest Download Bundle to disksave_to_disk('/tmp/elastic_security.zip',downloaded_bundle)
Package: appi
Another Portage Python InterfaceWhy notportage?Mainly, I was having hard time understanding the pythonportagemodule. I found the code
somewhat obscure and lacking documentation. So I decided to start an alternative, bringing my
approach of how I would like the API to be.So was bornappi. It is still at an early stage, but I hope someday it will have enough
features to enable portage-based distributions newcomers to use it and improve it.ExamplesAtom>>>fromappiimportQueryAtom>>>a=QueryAtom('portage')Traceback(mostrecentcalllast):File"<stdin>",line1,in<module>File"/home/tony/Workspace/Funtoo/appi/appi/atom.py",line76,in__init__atom_string,code='missing_category')appi.atom.AtomError:portagemaybeambiguous,pleasespecifythecategory.>>>a=QueryAtom('portage',strict=False)>>>a.list_matching_ebuilds(){<Ebuild:'sys-apps/portage-2.4.1-r1::gentoo'>,<Ebuild:'sys-apps/portage-2.4.3-r1::gentoo'>}>>>a<QueryAtom:'portage'>>>>b=QueryAtom('>=sys-apps/portage-2.4.2')>>>b<QueryAtom:'>=sys-apps/portage-2.4.2'>>>>b.list_matching_ebuilds(){<Ebuild:'sys-apps/portage-2.4.3-r1::gentoo'>}>>># Considering a second repository named "sapher" containing qtile ebuilds...>>>QueryAtom('=x11-wm/qtile-9999').list_matching_ebuilds(){<Ebuild:'x11-wm/qtile-9999::gentoo'>,<Ebuild:'x11-wm/qtile-9999::sapher'>}Versioning PolicyWe use the following version format:M.m.pMis the major versionmis the minor versionpis the patch versionWe may also package pre-releases (postfixed with_preN, whereNis the pre-release version)
and release candidates (postfixed with_rcN, whereNis the release candidate version).Starting from version 1.0.0,a major version bump means:Global refactoring of the code baseRemoval of features deprecated in the previous releasesA minor version bump means:New featuresExisting features improvementFeatures deprecation (raising warnings) which will be removed in the next major versionA patch version bump means:Bug fixesSecurity fixesThus, backward compatibility is maintained across minor versions, but broken at each
major version bump. However:Major version bumps should be very rareIf you pay attention to the few deprecation warnings that may appear across minor version bumps,
and fix them along the way, upgrading to a new major version will require no work at all.Support and patcheswillstill be provided for the last two minor versions before
the curent version.Starting from version 2.0.0, the main module will be namedappiMwhereMis the major
version number (eg.appi2,appi3, …). This will allow old software not using the
latest major version to stay available along with newer software using the latest major version.Before version 1.0.0,any minor version bump may break backward compatibility.ContributingSeeContributingpage.