Saravanan666/pypi-org huggingface dataset:
Package: setuptools-ocrd
setuptools_ocrdManage your Python package version throughocrd-tool.json.To use this, set theversionfield inocrd-tool.jsonand use this in yourpyproject.toml:[build-system]
requires = ["setuptools>=61.0.0", "wheel", "setuptools-ocrd"]

[project]
# ... any other options ...
dynamic = ["version"]Developer informationPlease refer toREADME-DEV.md.
Package: setuptools-openapi-generator
A setuptools extension for generating RESTful clients from OpenAPI schema at build time,
allowing for easy use of the API with static type checking.PyPIpip install setuptools_openapi_generatorSource codehttps://github.com/DiamondLightSource/setuptools_openapi_generatorReleaseshttps://github.com/DiamondLightSource/setuptools_openapi_generator/releasesTo generate an API client in your project, simply addsetuptools_openapi_generatorto thebuild-system.requiressection of yourpyproject.toml.Client generation can be configured via atoolentry in thepyproject.tomlas below:[build-system]requires=["setuptools","setuptools_openapi_generator"][tool.setuptools_openapi_generator]basedir="src/sample_project/apis/"sources=["https://raw.githubusercontent.com/OAI/OpenAPI-Specification/main/examples/v3.0/link-example.json","api_definitions/petstore.json"]The above example will generate two API clients, atsrc/sample_project/apis/link_exampleandsrc/sample_project/apis/petstorerespectively.
Package: setuptools-parcels
=================setuptools-parcels=================An alternative syntaxt to setuptools package_data argument.Improvements over package_data include:* simple way to include all non-python files found in packages-----Usage-----You can use setuptools-parcels by including it in your setup.py, as anadditional argument to setup`s setup_requires function, and anadditional parcels parameter:.. code:: pythonsetup(...# add it heresetup_reqires=["setuptools-parcels", "vcver"],parcels={})Without any configuration, parcels will search through all packages,find any non-python files, and include those.If the package_data is present, parcels will merge it's additions withthe existing values.
Package: setuptools-pep8
Setuptools pep8 commandOriginally based onhttps://github.com/johnnoone/setuptools-pylintThis package exposes thepep8style guide checker as a
sub-command of setup.py:$ cat setup.py
...
    setup(
        name='your project',
        setup_requires=['setuptools-pep8']
    )
....
$ cat setup.cfg
...
[pep8]
ignore=E225
...
$ python setup.py pep8
running pep8
./setup.py:41:1: W391 blank line at end of fileThis invokespep8and applies any configuration from yoursetup.cfgfile’s[pep8]section. Typical use cases
include simplification of continuous-integration job configurations.News0.9.0Release date: 29-Dec-2013Final major release before v1.0 (project goes into maint mode).Contains non-backwards-compatable changes!Bugfixes:Resolves clash with setuptools Command –verbose flagFeatures:All pep8 cmdline options can now be specified on thepython setup.py pep8command linepep8 return code is propagated to thepython setup.pycommand
return codeNon-Functional Changes:Drastic simplification of pep8 setuptools Command implementationMinor changes to testing code (adopt usage of process return code)Backwards Incompatable Changes:–pep8-output option has been removed. Replace usage of this with
shell redirection.–check-dirs option has been removed. Replace usage of this with
pep8’s –exclude option.Any users wishing to retain these features are advised to stay on
version 0.2.0.0.2.0Release date: 28-Dec-2013Stable build, promoted minor version. No functional changes.0.1.7Release date: 28-Dec-2013Enabled Travis-CI integration testingConfigured auto upload from Travis -> PyPI for tagged releasesMinor formatting tweaks0.1.6Release date: Not releasedMinor tweak to .rst syntax, fix rendering issues on PyPI0.1.5Release date: 3-Dec-2013Bugfix: missing NEWS.rst in manifest0.1.4Release date: 3-Dec-2013@yoloseem fixed indentation bugFixed setup.cfg parsing of include / exclude directives0.1.3Release date: 6-Oct-2013Fixed github issue #1: Setting pep8 directives in setup.cfg doesn’t workExposed –check-dirs= option to control which modules are checkedFixed incorrect handling of stdout/stderr when redirecting pep8 output to a file0.1.2Release date: 4-Oct-2013Fork ofhttps://github.com/johnnoone/setuptools-lintAdds in config parsing from setup.cfgSemantic versioning
Package: setuptools-pipfile
setuptools-pipfileDependency management via PipfileOverviewIn basic mode setuptools-pipfile does the following:Populatesinstall_requiresfrom the packages table.Populatestests_requirefrom the dev-packages table.Populatesdependency_linksfrom the source tables if needed by dependencies.Advanced configuration can be used to control:The path to the Pipfile.Variable interpolation.Removing indexes fromdependency_links.Activate and control populatingextras_require.Control populatingpython_requires.All documentation is locatedhere.
Package: setuptools-proto
setuptools-protosetuptoolsplugin to compile.protofiles usingpython-betterproto.PrerequisiteProtobuf compilerprotocPython 3.6+Enablesetuptools-protoIn either of the following scenarios,setuptools-protowill take effects.Option 1, installsetuptools-protousingpipor other tools:$pipinstallsetuptools-protoOption 2, requiresetuptools-protoinsetup_requireskeyword ofsetuptools.So, add it eithersetuptools.setup(setup_requires=['setuptools-proto'],)insetup.pyin a imperative fashion or[options]setup_requires=setuptools-protoinseutp.cfgin a declarative manner.ConfigurationProtobuf modulesTo letsetuptools-protoknow what to compile,
defineprot_modulesas aProtoModulelist.fromsetuptoolsimportsetupfromsetuptools_protoimportProtoModulemodule1=ProtoModule(['proto/sample/**/*.proto'],cwd='proto/sample',)module2=ProtoModule(['demo/grpc/echo.proto','demo/grpc/hello.proto'],cwd='demo/grpc',out_dir='proto',include_dirs=['demo/schema'],)setup(proto_modules=[module1,module2],)protoccompilerBy default,setuptools-protowill use the systemprotoccompiler.
If there's a custom install ofprotoc, which is not in thePATH,
You can point environment variablePROTOCto it,
or command line argument--protocto it.For example,$pythonsetup.py--protoc/path/to/protocbuild_protoExecuteAn extra commandbuild_protois added, to compile.prototo python code.
This command will be automatically run before commandbuild_py.
Package: setuptools-protobuf
protobuf support for setuptoolsPlugin forsetuptoolsthat adds support for compiling protobuf files.DependenciesThe plugin requires the externalprotocexecutable that is part of theprotobuf projectto be present.
On Debian systems, this executable is shipped in theprotobuf-compilerpackage.If theprotoc_versionoption is specified, the specified version of protoc
will be downloaded from github. When it is not specified, aprotocbinary is
expected to be present in the environment. You can override the binary with the
PROTOC environment variable.Optionally, it can also generate typing hints if themypyextra is selected.UsageYou can configuresetuptools-protobufin eithersetup.py,setup.cfgorpyproject.toml.setup.pyfromsetuptools_protobufimportProtobufsetup(...setup_requires=['setuptools-protobuf'],protobufs=[Protobuf('example/foo.proto')],)setup.cfg...[options]setup_requires=setuptoolssetuptools-protobufpyproject.toml[build-system]requires=["setuptools","setuptools-protobuf"][tool.setuptools-protobuf]protobufs=["example/foo.proto"]# Require the generation of typing hints:mypy=true# Optionally, set the specific protoc version to use:protoc_version='25.1'GitHub actionsTo install protoc in a GitHub action, you can use thesetup-protocaction:-name:Install Protocuses:arduino/setup-protoc@v2
Package: setuptools_pyflakes
AboutThis is a plugin for setuptools that integrates pyflakes.  Once installed,
“python setup.py flakes” will run pyflakes on all of the modules in your
project.InstallationWith easy_install:easy_install setuptools_pyflakesAlternative manual installation:tar -zxvf setuptools_pyflakes-X.Y.Z.tar.gz
cd setuptools_pyflakes-X.Y.Z
python setup.py installWhere X.Y.Z is a version number.UsageTo use this plugin, you must first package your python module withsetup.pyand use setuptools.  The former is well documented in the
distutils manual:http://docs.python.org/dist/dist.htmlTo use setuptools instead of distutils, just editsetup.pyand
changefrom distutils.core import setuptofrom setuptools import setupThen, if this plugin is installed, “python setup.py flakes” will work.Automatically installing setuptools_pyflakesYou can make sure that anyone who uses your setup.py, and who invokes “python
setup.py flakes”, automatically gets this plugin installed, by adding asetup_requiresargument.:setup_requires=[]
# setuptools_pyflakes is required to make "python setup.py flakes" work.
if 'flakes' in sys.argv[1:]:
  setup_requires.append('setuptools_pyflakes')

setup(...,
  setup_requires = setup_requires,
  ...)ReferencesHow to distribute Python modules with Distutils:http://docs.python.org/dist/dist.htmlSetuptools documentation:http://peak.telecommunity.com/DevCenter/setuptoolsThanks to Yannick Gingras for providing the prototype for this
README.rst.
Package: setuptools-pyproject-migration
setuptools-pyproject-migrationIntroductionpyproject.tomlrepresents the new era of Python packaging, but many old
projects are still usingsetuptools. That's where this package comes in: just
install it, run it, and it will print out a nicely formattedpyproject.tomlfile with the same metadata that you had insetup.pyorsetup.cfg.Or at least, that's the goal. The project is currently a work in progress with
only partial support for all the attributes that might exist in a setuptools
configuration, so this won't yet work for anything complex. Feel free to file
an issue to highlight anything that needs to be added!Installation and usageThere are two different ways to install this project. You can use either or both
depending on what you prefer.Standalone applicationTo installsetuptools-pyproject-migrationas an application, we recommend
usingpipx(though of course you can also do
this withpip install --useror in a virtual environment of your choice).
First make sure you have pipx installed, then runpipx install setuptools-pyproject-migrationAfter that, in any directory that has asetup.pyand/orsetup.cfgfile, you
can runsetuptools-pyproject-migrationand it will print out the content ofpyproject.tomlas computed from yoursetup.pyand/orsetup.cfg. Runningsetuptools-pyproject-migration -hwill
print a brief usage summary.You can also install and run the application in one go as follows:pipx run setuptools-pyproject-migrationVirtual environmentOr you can usesetuptools-pyproject-migrationin a virtual environment you use
to develop your project. Activate your virtual environment and then runpython -m pip install `setuptools-pyproject-migrationand then runningpython setup.py pyprojectwill print out the content of yourpyproject.tomlfile.HistoryInspired bya conversation on Mastodon.
Package: setuptools-qmesh
setuptools-qmesh provides setuptools extensions that facilitate installation of qmesh packages.InstallationYou do not have to install setuptools-qmesh yourself. setuptools-qmesh will be automatically downloaded from PyPI when required, during installation of other qmesh packages.See theqmesh synoptic manualfor more information.Development, Maintenance and Licencesetuptools-qmesh is developed and maintained byAlexandros AvdisandJon Hill.
Please see fileAUTHORS.mdfor more information.setuptools-qmesh is distributed under GPL v3.
The fileLICENCEcontains a complete copy of the licence.The package setuptools-qmesh is open-source.
The source code is freely available to download and adapt, subject to the conditions stated in theLICENCEfile.
However, we adopted a closed-development approach, where maintenance and development is carried out by the package originators.
We have opted for this approach to limit the resources needed for development. A larger development team necessitates larger management structures and significant CI/CD expenditure.
Larger management structures will absorb time for other exciting and useful research, while CI/CD expenditure could threaten our aim to offer a focused package, at no monetary costs to the users.DocumentationYou can access relevant documentation through the following avenues:Theqmesh website.Theqmesh synoptic manual.Thesetuptools-qmesh reference manual.
Package: setuptools-rust-tomlgen
Setuptools plugin for generating Rust Cargo.toml Filessetuptools-rust-tomlgenis a plugin forsetuptoolsandsetuptools-rust. It adds thetomlgen_rustcommand which generates RustCargo.tomlfiles from the contents ofsetup.py.UsageInstall from pip:$pipinstallsetuptools-rust-tomlgenCreate a project which contains both asetup.pyfile and some Rust.rsfiles, such asthe example project.GenerateCargo.tomlfiles viasetup.py:$pythonsetup.pytomlgen_rustMetadataThe package name will be generated from the position of the extension within
the Python package. The same version is used as the one declared insetup.pyorsetup.cfg.The authors list is generated after theauthorandauthor_emailoptions
fromsetup.py/setup.cfg, but can also be overriden using theauthorskey in the[tomlgen_rust]section ofsetup.cfg:[tomlgen_rust]authors=Jane Doe <jane@doe.name>John Doe <john@doe.name>The library name is a slugified variant of the extension package name, to
avoid name collisions within the build directory.As a safety,publish = falseis added to the[package]section
(you wouldn't publish an automatically generated package,would you ?!).OptionsUse--force(or addforce = trueto the[tomlgen_rust]section ofsetup.cfg) to force generating a manifest even when one already exists.Use--create-workspaceto create a virtual manifest at the root of your
project (next to thesetup.pyfile) which registers all of the extensions.
This way, genericcargocommands can be run without leaving the root of
the project.If--create-workspaceis enabled, a.cargo/configfile will also be
created to forcecargoto build to the temporary build directory. Use--no-configto disable.DependenciesTo specify dependencies for all extensions, add them to the[tomlgen_rust.dependencies]section of your setuptools configuration file
(setup.cfg), as you would normally in yourCargo.tomlfile. Here is
probably a good place to addpyo3as a dependency.To specify per-extension dependency, create a section for each extension
([tomlgen_rust.dependencies.<DOTTEDPATH>], where<DOTTEDPATH>is the
complete Python path to the extension (e.g.hello-english). Extension
specific dependencies are addedafterglobal dependencies.Note that, since all projects are built in the same directory, you can also
declare all dependencies in the[tomlgen_rust.dependencies],as they will
be built only once anyway.Automatic generation at each buildIf you intend to regenerate manifests everytime the library is built, you can
addCargo.tomlandCargo.lockto your.gitignorefile.Then, make suretomlgen_rustis run beforebuild_rusteverytime by
adding aliases to yoursetup.cfgfile:[aliases]build_rust=tomlgen_rust -f build_rustclean_rust=tomlgen_rust -f clean_rustbuild=tomlgen_rust -f buildclean=clean_rust -f clean
Package: setuptools-scm
setuptools_scmaboutsetuptools-scmextracts Python package versions fromgitorhgmetadata instead of declaring them as the version argument
or in an SCM managed file.Additionally,setuptools-scmprovides setuptools
with a list of files that are managed by the SCM(i.e. it automatically addsall ofthe SCM-managed files to the sdist).Unwanted files must be excluded viaMANIFEST.in.pyproject.tomlusageThe preferred way to configuresetuptools-scmis to author
settings in atool.setuptools_scmsection ofpyproject.toml.This feature requires setuptools 60 or later.
First, ensure thatsetuptools-scmis present during the project's
build step by specifying it as one of the build requirements.[build-system]requires=["setuptools>=60","setuptools-scm>=8.0"]That will be sufficient to requiresetuptools-scmfor projects
that supportPEP 518likepipandbuild.To enable version inference, you need to set the version
dynamically in theprojectsection ofpyproject.toml:[project]# version = "0.0.1"  # Remove any existing version parameter.dynamic=["version"][tool.setuptools_scm]Additionally, a version file can be written by specifying:[tool.setuptools_scm]version_file="pkg/_version.py"Wherepkgis the name of your package.If you need to confirm which version string is being generated or debug the configuration,
you can installsetuptools-scmdirectly in your working environment and run:$python-msetuptools_scm#Toexploreotheroptions,try:$python-msetuptools_scm--helpFor further configuration see thedocumentation.Interaction with Enterprise DistributionsSome enterprise distributions like RHEL7
ship rather old setuptools versions.In those cases its typically possible to build by using an sdist againstsetuptools_scm<2.0.
As those old setuptools versions lack sensible types for versions,
modernsetuptools-scmis unable to support them sensibly.It's strongly recommended to build a wheel artifact using modern Python and setuptools,
then installing the artifact instead of trying to run against old setuptools versions.Code of ConductEveryone interacting in thesetuptools-scmproject's codebases, issue
trackers, chat rooms, and mailing lists is expected to follow thePSF Code of Conduct.Security ContactTo report a security vulnerability, please use theTidelift security contact.
Tidelift will coordinate the fix and disclosure.
Package: setuptools-scm-about
This is asetuptools_scmplugin
that adds support for __about__.py files.If version cannot be resolved via SCM, the fallback registered by this plugin will be called.
It will try to find the__about__.pyfile (using the**/__about__.pyglob pattern) that defines
the__version__variable.Since there is no SCM metadata available, package will returnVERSION.dev0+unknownwhere VERSION is a version
from__about__.py.UsageAdd'setuptools_scm_about'to thesetup_requiresparameter in your
project’ssetup.pyfile:setup(...,use_scm_version={'write_to':'myproject/_version.py'},setup_requires=['setuptools_scm','setuptools_scm_about'],...,)Define__version__inmyproject/__about__.py:__version__=1.0Import__version__inmyproject/__init__.pyfor external access:try:from._versionimportversionas__version__exceptImportError:from.__about__import__version__
Package: setuptools-scm-azure-pipelines
setuptools_scm_azure_pipelinesDescriptionA stupidly simplesetuptools_scmplugin that generatesPEP-440 post-releasespackages versions prefixed
with the Azure Pipelines${BUILD_BUILDID}for builds that happen on non-tagged git commits.BUILD_BUILID, or rather$(Build.BuildId)in the Azure Pipeline lingo, is the variable that is set
by Azure Pipelines when a build is running.When this variable is present and you are using this tool, your package's version will be:{tag}, e.g.1.2.3when you are building on a tag ("exact version"),{tag}.post{BUILD_BUILDID}, e.g.1.2.3.post12345when you are building an intermediate version ("on-commit"),This allows your fellow developpers to get the "latest" version of a package, no matter what.You might not want that to happen everytime, though. In that case, don't forget to pin you dependencies correctly using one of:pip-toolsPipenvPoetryUsageUsage inpyproject.tomlSet it up inpyproject.toml[build-system]section like this:[build-system]requires=["setuptools>=45","wheel","setuptools_scm>=6.2","setuptools_scm_azure_pipelines>=1.0"][tool.setuptools_scm]local_scheme="no-local-version"version_scheme="post-release-azure-build-id"
Package: setuptools-scm-build-number
This is asetuptools_scmplugin
that provides thenode-date-and-build-numberlocal scheme.Build number is read from theBUILD_NUMBERenvironment variable.UsageAdd'setuptools_scm_build_number'to thesetup_requiresparameter in your
project’ssetup.pyfile:setup(...,use_scm_version={'local_scheme':'node-date-and-build-number'},setup_requires=['setuptools_scm','setuptools_scm_build_number'],...,)
Package: setuptools-scm-git-archive
This plugin is obsolete. ``setuptools_scm >= 7.0.0`` supports Git archives by itself.Migration guideChange the contents of the.git_archival.txtfile in the root directory of your repository from:ref-names: $Format:%D$to:node: $Format:%H$
node-date: $Format:%cI$
describe-name: $Format:%(describe:tags=true)$
ref-names: $Format:%D$Removesetuptools_scm_git_archivefrom your project’s dependencies (e.g. thesetup_requireslist in yoursetup.pyfile).
Package: setuptools-scm-git-semver
setuptools_scm_git_semverSemVer-compatible hooks forsetuptools_scm.This package was created becausesetuptools_scmproducesPEP 440compliant version numbers,
which are not always compatible with SemVer.UsageUsage is no different from normal setuptools_scm -- this package just adds 1
version scheme and local scheme each:guess-next-rc: Returns the next version as RC when not on a clean tagtime-dot-node: Returns a local version of +.In addition, if a version tag from SCM is not available, the content of
VERSION.txt is used.Example configurations to get version numbers that are both valid python
package versions and SemVer versions, and fall back on what's in VERSION.txt if
not in SCM:Using pyproject.toml:[build-system]requires=["setuptools","setuptools_scm","setuptools_scm_git_semver",]build-backend='setuptools.build_meta'[tool.setuptools_scm]version_scheme="guess-next-rc"local_scheme="time-dot-node"normalize=falsewrite_to="VERSION.txt"ReleasesThe package should be released to PyPI. The first release will be performed manually, and CI will be
written later.
Package: setuptools_shim
Abstract build system shim providing setup.pyThis repository provides a shim so that projects using non-setuptools build
systems which can be built using the PEP XX [#pepxx] abstract build interface,
can be installed by older pip versions which do not implement the interface.Free software: Apache licenseDocumentation:http://docs.openstack.org/developer/setuptools_shimSource:http://git.openstack.org/cgit/openstack/setuptools_shimBugs:http://bugs.launchpad.net/setuptools_shimUsageCopyshim.pyfrom this project into your source tree assetup.pyOnce this is done, callingsetup.pywill trigger easy-install to makesetuptools_shimand its dependencies as well as the bootstrap requirements
frompypa.jsonavailable at build/install time.