Saravanan666/pypi-org huggingface dataset:
Package: yaclifw
Introductionyaclifwis a framework for building CLI tools.DependenciesDirect dependencies of yaclifw are:argparseInstallationTo installyaclifw, run:$ python setup.py installor using pip, run:$ pip install yaclifwTo upgrade your pip installation, run:$ pip install -U yaclifwUsageThe list of available commands can be listed with:$ yaclifw -hFor each subcommand, additional help can be queried, e.g.:$ yaclifw example -hExtending yaclifwThe easiest way to make use of yaclifw is by cloning the
repository and modifying the main.py method to include
your own commands.Contributingyaclifw followsPEP 8, the Style Guide for Python Code. Please check your
code withpep8orflake8, the Python style guide checkers, by runningflake8-v.orpep8-v..Running testsThe tests are located under thetestdirectory. To run all the tests, use
thetesttarget ofsetup.py:python setup.py testUnit testsUnit tests are stored under thetest/unitfolder and can be run by calling:python setup.py test -t test/unitUnit tests are also run by theTravisbuild on every Pull Request opened
against the main repository.Licenseyaclifw is released under the GPL.Copyright2014, The Open Microscopy Environment
Package: yaclipy-tools
yaclipy-toolsAn extensible, asyncio interface to subprocesses, plus a set of wrappers around common system tools that works well withyaclipyToolscurldockerffmpegfirebasegcloudgitgpggraphvizgrepkubectlmd5nginxopensslshasumThe set of tools can easily be extended by subclassing SysToolProcTaskThis creates an asynchronous connection to a sub-process.  It is based upon loop.subprocess_exec().await ProcTask('diff', 'README.md', 'README.md')
0For more complicated interactions, plugins are used.await ProcTask.using(Lines(1))('ls', '-al')
[...]The Lines plugin captured stdout (1) and return a list of lines.
If no plugins want to return a value then the default behavior is to return the returncode as seen in the above example.
If multiple plugins want to return a value then they are returned as a tuple:await ProcTask.using(Lines, Lines(2))('ls', '-al')
([...], [...])The first value of the tuple contains the lines from stdout AND stderr, whereas the second list only contains stderr lines.EchoThe Echo plugin prints to the print_ext Printer().  By setting the context you can create nice, grouped command output.LinesCapture the output and return a list of stringsOneLineCapture the output but only return one of the linesInputSend data to stdin of the processLogCapture the output and send it to a file (or other io.Stream)WatchAsk for the output to be captured so that you can use it asynchronously.SysToolSysTool build upon ProcTask by integrating it with yaclipy and adding more user-facing features, such as:configurable command location (no more environment variables)Tool availability and version check.Helpful info about how to install missing tools.Table of ContentsInstallationLicenseInstallationpip install yaclipy-toolsLicenseyaclipy-toolsis distributed under the terms of theMITlicense.
Package: yaclog
YaclogYet another changelog command line toolLogo by Erin CassidyInstallationInstall and update usingpip:$pipinstall-UyaclogUsageFor usage from the command line, yaclog provides theyaclogcommand:Usage: yaclog [OPTIONS] COMMAND [ARGS]...

  Manipulate markdown changelog files.

Options:
  --path FILE  Location of the changelog file.  [default: CHANGELOG.md]
  --version    Show the version and exit.
  --help       Show this message and exit.

Commands:
  entry    Add entries to the changelog.
  format   Reformat the changelog file.
  init     Create a new changelog file.
  release  Release versions.
  show     Show changes from the changelog file
  tag      Modify version tagsExample workflowCreate a new changelog:$yacloginitAdd some new entries to the "Added" section of the current unreleased version:$yaclogentry-b'Introduced some more bugs'$yaclogentry-b'Introduced some more features'Show the current version:$yaclogshowUnreleased

- Introduced some more bugs
- Introduced some more featuresRelease the current version and make a git tag for it$yaclogrelease0.0.1-cRenamed version "Unreleased" to "0.0.1".
Commit and create tag for version 0.0.1? [y/N]: y
Created commit a7b6789
Created tag "0.0.1".
Package: yaclog-ksp
yaclog-kspA command line tool based onyaclogfor converting markdown changelogs toKerbalChangelogconfig files.Logo by Erin CassidyInstallationrunpip install yaclog-kspUsageUsage: yaclog-ksp [OPTIONS]

  Converts markdown changelogs to KSP changelog configs.

Options:
  --path FILE        Location of the changelog file.  [default: CHANGELOG.md]
  -o, --output FILE  Output file to write to. Uses
                     'GameData/{name}/Versioning/{name}ChangeLog.cfg' by
                     default.

  -n, --name TEXT    The name of the mod. Derived from the current directory
                     by default.

  --version          Show the version and exit.
  --help             Show this message and exit.for example, runningyaclog-ksp --path MyLog.md -n "My KSP Mod"would output toGameData/MyKSPMod/Versioning/MyKSPModChangeLog.cfgInput files are in markdown, and use a certain syntax to be readable by the tool. Metadata is included in a table at the
top of the file (which row you make the header doesnt matter). Each version is an subheading with the version, an
optional date, and the KSP version as a tag on the end in bracketsExample Changelog:# ChangelogThis is the changelog for my cool mod!

| modName | MyCoolMod     |
| ------- | ------------- |
| license | CC-By-SA      |
| website | Example.com   |
| author  | A cool person |## 1.0.0 - 2020-04-16 [KSP 1.11]First full release### Fixed-Nyan Cat now has correct music### Added-Multiplayer## 0.9.1 [KSP 1.10.1]Supported versions: 0.2.0 beta to 1.10.x### ChangedA very complicated thing that I can't easily explain in bullet points, 
but this paragraph works pretty well to get the point across!-Another thing that has multiple specific items-this bullet point*and this other one
    + oh and another one!### Removed-Herobrine
Package: yacloud
Р”Р»СЏ РєР»Р°СЃСЃРµ cloudfile, РЅР°СЃС‚СЂРѕР№ РїРµСЂРµРјРµРЅРЅС‹Рµ РѕРєСЂСѓР¶РµРЅРёСЏ
YC_API_KEY - РєР»СЋС‡ РїСЂРѕСЃС‚РѕРіРѕ РґРѕСЃС‚СѓРїР°
YC_API_SECRET - СЃРµРєСЂРµС‚ РґР»СЏ РїСЂРѕСЃС‚РѕРіРѕ РґРѕСЃС‚СѓРїР° Рє Р±Р°РєРµС‚Р°Рј
Package: yacluster
yacluster========yacluster is a Python library which does `distance-based clustering`_ for 2D points. Only Python 3.4+ is officially supported, though other versions may work too. The project uses `semantic versioning`_ and is licensed under `the MIT license`_.Usage-----The main utility is the ``yacluster.cluster`` function which takes two arguments:* an iterable which yields two-element point tuples, each containing:- a two-element tuple with X and Y coordinates;- the actual object being clustered (or its identifier);* a distance threshold; if a point is included into a cluster, it must be closer to its centroid than this value.The function returns an iterable of two-element cluster tuples, each containing:* a two-element tuple with X and Y coordinates of the cluster center;* a list of objects belonging to the cluster.Cluster’s centroid is defined as average coordinates of the cluster’s members.Example-------.. code-block:: pythonfrom yacluster import clusterpoints = [((1, 1.0), 'Foo'),((1.0, 2), 'Bar'),((2.0, 2.0), 'Baz'),]threshold = 1.1expected_result =  [((1.0, 1.5), ['Foo', 'Bar']),((2.0, 2.0), ['Baz']),]assert expected_result == list(cluster(points, threshold))Development-----------Development requirements are listed in the ``requirements-development.txt`` file.To run tests, execute ``./tests.py``.Coding style is checked using `flake8 3.x`_... _distance-based clustering: https://developers.google.com/maps/articles/toomanymarkers#distancebasedclustering.. _flake8 3.x: http://flake8.pycqa.org/en/latest/.. _semantic versioning: http://semver.org.. _the MIT license: LICENSE
Package: yaco.applyfun
IntroductionThis package allows developers to define functions and apply them to sets of objects through a zope3 view. The sets of objects can be subtrees of the ZODB, or can be defined by a query to portal_catalog.To use it, you just have to add two lines to your buildout, one to add yaco.applyfun to the eggs section of the main part ([buildout]), and one in the zcml section of the instance part that has to have the view.Then, you have de @@applyfun view available on any content.To add functions, you can define them in the walker_funcs.py module of the product, or you can define them in any other module with the same structure (functions plus a “functions” dict) and plug it in through the config.py module of the product. The docstring of the functions will be available as help in the view.Changelog1.0 - UnreleasedInitial release
Package: yaco.deliverancethemeselector
IntroductionThis is a Plone product that provides a way to select a theme for a specific
section of your site. The theme will by applied at publication time using a
custom header in conjuction with deliverance as proxy.This product use theplone.app.registrypackages to provide a simlpe way to
add new entries in the product configuration for custom products using
genericsetup.Table of contentsIntroductionInstalationUsing BuildoutDependenciesRepositorySponsorshipChangelogInstalationUsing BuildoutAddyaco.deliverancethemeselectorto the list of eggs to install, e.g.:[buildout]
...
eggs =
    ...
    yaco.deliverancethemeselectorTell the plone.recipe.zope2instance recipe to install a ZCML slug:[instance]
recipe = plone.recipe.zope2instance
...
zcml =
    ...
    yaco.deliverancethemeselectorRe-run buildout, e.g. with:$ ./bin/buildoutDependenciesplone.app.registryRepositorysvn repositoryhttp://svn.plone.org/svn/collectiveSponsorshipThis product was sponsored by “Universidad de Extremadura” (www.unex.es)
and Yaco Sistemas (www.yaco.es)Changelog1.0a1 - 2010-06-16Initial release [nueces]
Package: yaco.hghooks
Contentsyaco.hghooksChanges0.1.2 (unreleased)0.1.1 (2010-10-18)0.1.0 (2010-10-17)yaco.hghooksyaco.hghooks is a set of extensions to hghooks trac hooks.It adds spanish translations of the close and see ticket actions and adds
verify and merge actions.Changes0.1.2 (unreleased)Do not import yaco.hghooks in install time since our dependencies are not
available yet. Instead, move the version information directly to the
setup.py file.0.1.1 (2010-10-18)Require a specific minimum version of hghooks0.1.0 (2010-10-17)Initial release
Package: yaconf
# yaconfyet another Python configuration library## FeaturesNo frills, no fuss:* Python 3.6+ and no external dependencies.* Single file implementation: Import the package or just copy `yaconf.py` into your project.* Use any configuration source: any function that returns a `dict` will do.* Reads JSON files by default, but `configparser` or any other parser can be dropped in with a keyword argument.* Hierarchical configuration: Look for configuration keys in one config source after another, e.g.,- first check `.myappconf` file,- then `~/.config/myapp/.myappconf`,- finally fall back on defaults.* Sane defaults for config file paths:- `~/.config/myapp/.myappconf` on Linux and MacOS- `%LOCALAPPDATA%\myapp\.myappconf` on Windows* Optionally register a modifier function to arbitrarily change values after loading (e.g., change datatypes, check consistency, etc).## Examples### Basic setup```pythonimport yaconfconf = yaconf.get_file_reader('myapp')conf.load()# reading from .myappconf if available, then ~/.config/myapp/.myappconfconf['ready to go']conf.get('ready to go', default='fallback')```### Add more configuration sources```pythondef get_default_config():return {'i': 123, 'b': 'default string'}# Add this configuration with lowest priorityconf.loaders.append(get_default_config)def get_top_priority_config():return {'b': 'other string'}# And this one with highest priorityconf.loaders.push(get_top_priority_config)# To include the new configuration sourceconf.load()assert conf['i'] == 123assert conf['b'] == 'other string'```### The ConfigReader is a Mapping```pythonassert dict(conf) == {'i': 123, 'b': 'other string'}```### Add a modify function```pythondef modify(d):d['i'] += 3del d['b']d['x'] = 'new'conf.modify = modifyconf.load()assert dict(conf) == {'i': 126, 'x': 'new'}```## LicenseFree software: MIT license## CreditsThis package was created with [Cookiecutter][1] and the [`audreyr/cookiecutter-pypackage`][2] project template.[1]: https://github.com/audreyr/cookiecutter[2]: https://github.com/audreyr/cookiecutter-pypackage=======History=======0.2.0 (2019-04-10)------------------* Allow for a modify function to be added to ConfigReader.* Remove the levels property on ConfigReader.* Make ConfigReader follow the Mapping protocol.* Rename Decoder -> Parser.0.1.0 (2019-04-09)------------------* First release on PyPI.
Package: yaconfig
yaconfigPython package to assist configuration of Python software.InstallationTo install the latest release:pip3installyaconfigUsageThis package is intended to be used by other package to assist their configuration. The recommended workflow follows:Add a config module. Its purpose should be to define the configuration variables (the metaconfig) and to provide a
single instance of the actual configuration (the values) for your application. If you want to implement a more complex
logic to handle multiple configuration, you can do it here. Simple example:"""File config.py"""importyaconfigmetaconfig=yaconfig.MetaConfig(yaconfig.Variable("text",type=str,default="Hello world",help="Text to output"))# Get a default configuration, which should be overridden when the execution startsconfig=yaconfig.Config(metaconfig)In the entry point of your program, load the previous module and initialize the config using the desired method.
The variables can be accessed from now on. Example:"""File main.py"""fromconfigimportconfig# Just need the config object of the previous module# Use a relative import instead if intended to run as a package# from .config import configtry:config.load_json("config.json")exceptFileNotFoundError:print("config.json file not found. Using the default configuration instead.")print(config["text"])Note that if that file can be loaded as a module, you should avoid initializing the config. You can use__main__or
build a launching script to prevent this.To document the configuration, you can use the methods of the metaconfig variable you have defined. This can be done
manually from the interpreter or automated by writing a script. Some examples follow:fromconfigimportmetaconfig# Or wherever the config was placedmetaconfig.generate_json_example()# Generate a config.example.json filemetaconfig.generate_environment_example()# Generate a environment.example.sh filemetaconfig.interactive_json()# Prompt the user to generate a config.json filemetaconfig.interactive_environment()# Prompt the user to generate a environment.sh file
Package: yaconfigobject
yaconfigobjectYet Anoter Configuration Object, this time using YAML.A Python package that provides application wide configuration as an object,
where all configuration items are accessible as attributes directly:fromyaconfigobjectimportConfigCONFIG=Config()property=CONFIG.topic.subtopicConfigurations are stored in a YAML file inside themodule/configdirectory
of the application. A file calledconfig.yamlexisting in the applications
current working directory will take precedence over the packaged file (in theconfigdirectory).Use in a moduleTo make sure every piece of code has access to the same configured information,
it is recommended to instantiate aConfigobject in the modules__init__.pyfile. TheConfigobject needs to be present before any other imports take
place.An example__init__.py:fromyaconfigobjectimportConfigCONFIG=Config('module.yaml')from.module_mainimport*Advanced usageSeveral options might help you adapting theConfigclass to your needs.Defining search pathsTo tellyaconfigobject.Config()where to search for config files, thepathskeyword argument can be specified as a list:CONFIG=Config(paths=['~','~/.local/share/my_app'])Using custom config file namesFor applications where different parts use a separate configuration, it is
highly recommended to use a custom file name:CONFIG=Config(name='my_app.yaml')Adding values in codeOf course you can also specify config values through code:fromyaconfigobjectimportConfigstatic_config=Config(database='sqlite:///:memory:')CONFIG=Config(name='my_app.yaml')CONFIG.update(static_config)Loading config values from environment variablesyaconfigobjectwill try to load config values from environment variables
prefixed with the uppercase module or application name when initialising aConfigobject.CONFIG=Config(name='my_app.yaml')All environment variables starting withMY_APPwill be considered a config
value. Config items from the environment will always take precedence.NOTE:When using environment variables, config item identifiers cannot
contain underscores(_)! The app / module name is the only exception.=======
History1.2.3 (2020-04-28)First release on PyPI.
Package: yacore
yacoreYetAnotherCORElibraryReasonReduce daily routine to start new service.Reduce errors on copy/paste things from previous projects.FeaturesBuild on top offacet,cockandgiveme. This meansservices,configurationanddependency injection.Flexible installation (install only what you need for current service, e.g.pip install yacore[db-postgresql,net-http])Couple backends for databases, logging, networking and whatever in strict service-like style.Current implementation matrixdatabaseloggingnetworkexecutorspostgresstdlibhttpx + fastapi + hypercornthread pool executorloguruRequirementspython 3.9+UsageYou can start new project from scratch with cookiecutter template via:cookiecutter gh:pohmelie/cookiecutter-yacoreRead more atcookiecutter-yacore.DocumentationTBDLicenseyacoreis offered under MIT license.DevelopmentInstallationpipinstall-e./[dev]Run testsSince coverage issue/feature, plugins coverage is broken by default.Workaround:COV_CORE_SOURCE=yacoreCOV_CORE_CONFIG=.coveragercCOV_CORE_DATAFILE=.coverage.eagerpytest
Package: yaco.recipe.cert
Contentsyaco.recipe.certUsageChanges0.1.1 (2011-03-21)0.1.0 (2011-03-21)yaco.recipe.certBuildout recipe that creates self signed certificates, useful for adding SSL support to your
development deployment.It needs the openssl binary installed in your system.Tests need to be written.Use at your own risk and specially, use real certificates in production.UsageExample usage:[buildout]
parts = mycert

[mycert]
recipe = yaco.recipe.cert
hostname = test.example.com
country = US
city = Springfield
organization = Example Corp.
locality = SpringfieldAfter running buildout you will have your self signed certificate in the parts directory.Changes0.1.1 (2011-03-21)Fix package name0.1.0 (2011-03-21)Initial version
Package: yaco.recipe.medialinker
Contentsyaco.recipe.medialinkerChangesyaco.recipe.medialinkerThis is just a buildout recipe that creates symbolic links for media files in
Django projects.The only needed option of the part that uses this recipe is the ‘media-eggs’,
which is a space separated list of eggs that contains media files.Tests need to be written.Use at your own risk.Changes0.1.0 (2010-12-22)Initial version
Package: yaco.recipe.patch
yaco.recipe.patch=================.. contents::- Code repository: git://github.com/ant30/yaco-recipe-patch.git- Report bugs at http://github.com/ant30/yaco.recipe.patch/issuesDetailed Documentation**********************Supported options=================The recipe supports the following options:patchPath to patchpatchlocationLocation to apply patchbinary-patchLocation of patch binary. Use patch in $PATH by default if any is specified.Example usage=============We'll start by creating a buildout that uses the recipe::>>> write('buildout.cfg',... """... [buildout]... parts = testpatch...... [testpatch]... recipe = yaco.recipe.patch... patch = %(patch)s... patchlocation = %(patchlocation)s... """ % { 'patch' : 'patch/example-test.patch', 'example/' : 'value2'})Running the buildout gives us::>>> print 'start', system(buildout)Installing testpatch.Contributors************"Antonio Pérez-Aranda Alcaide", ant30Change history**************0.3.2.1 (2011-01-09)------------------- Upload package as sdist0.3.2 (2010-11-12)------------------- Remove update functionality, it isn't trivial if path has changed or disappeared0.3.1 (2010-11-12)------------------- Try to fix pypi published link0.3 (2010-07-23)----------------- Fix rst doc0.2 (2010-07-23)----------------- Patch and reverse patch on uninstall, fix doc0.1 (2010-07-23)----------------- Created recipe with ZopeSkelDownload********
Package: yaco.recipe.pycairo
Contentsyaco.recipe.pycairoChanges0.1.1 (2010-11-17)0.1.0 (2010-11-17)yaco.recipe.pycairoThis is just a recipe for compiling pycairo from a buildout.The only parameter is pkg-config-path which is the directory
with the cairo pkgconfig files.Tests need to be written.Use at your own risk.Changes0.1.1 (2010-11-17)Added MANIFEST file0.1.0 (2010-11-17)Initial release
Package: yaco.recipe.uwsgi
Contentsyaco.recipe.uwsgiChanges0.2.0 (2011-04-28)0.1.0 (2010-08-11)yaco.recipe.uwsgiThis is just a recipe for compiling uwsgi from a buildout.The only parameter is uwsgi-location which is the directory
with the uwsgi sources.Tests need to be written.Use at your own risk.Changes0.2.0 (2011-04-28)Add support for uwsgi >= 0.9.6.6 and remove support for older versionsWorkaround to make compile it under gcc 4.6.0 by removing the -Werror cflag0.1.0 (2010-08-11)Initial release
Package: yaco.releaser
zest.releaser addonhttp://pypi.python.org/pypi/zest.releaseris collection of command-line programs to help you
automate the task of releasing a software project which can be used for
non-Python projects too like buildouts.yaco.releaser is a very simple extension which allow append extra text to the default commit messages.It’s usefull for us because in Yaco is mandatory to mention a ticket to commit to a project.Contentszest.releaser addonInstallationUsageDevelopment notesTODOCreditsChangelogInstallationJust a simpleeasy_install yaco.releaseris enough.Alternatively, buildout users can install yaco.releaser as part of a
specific project’s buildout, by having a buildout configuration such as:[buildout]
parts = releaser

[releaser]
recipe = zc.recipe.egg
eggs = yaco.releaserUsageFollowhttp://pypi.python.org/pypi/zest.releaserdocumentationIn the process ofprereleaseorpostrealeaseyou will be wondered about adding
extra text to the commit message.Warning: Therelease(so fullrelease neither) are not supported yet, ie. you cannot add and extra
to the message when creating the new tag.Development notesThe svn source can be found athttps://svn.plone.org/svn/collective/yaco.releaser/trunk. If you have access
to the collective, you can fix bugs right away. Bigger changes on a branch please and mail pcaro_yaco.es about it :-)TODOAdd tests.Support for release and fullrelease commands.Do less interative. Maybe reading for enviroment.CreditsPablo Caro Revuelta(Yaco Sistemeas) is the
originator and main author.Changelogç (2010-06-05)Initial release