Saravanan666/pypi-org huggingface dataset:
Package: setuppy-generator
Installation$[sudo]pipinstallsetuppy-generatorProssetup.pygeneratorcreate multiple setup.py files - dev/prod, github/pypi, etcpython classes/cliFeatureskeyfile/environment variablenamecurrent directory basename or$SETUP_NAMEversion$SETUP_VERSIONurl$SETUP_URLclassifiersclassifiers.txt,$SETUP_CLASSIFIERSdescription$SETUP_DESCRIPTIONkeywords$SETUP_KEYWORDSlong_descriptionREADME.md/README.rst,$SETUP_LONG_DESCRIPTIONlong_description_content_typetext/markdowniflong_descriptionis.mdfileinstall_requiresrequirements.txt,$SETUP_INSTALL_REQUIRESpackagessetuptools.find_packages(),$SETUP_PACKAGESpy_modulespython files in a current directory,$SETUP_PY_MODULESscriptsscripts/*files,$SETUP_SCRIPTSExamplesproject-name.py/
├── classifiers.txt
├── module.py
├── package
|   └── __init__.py
├── README.md
├── requirements.txt
└── scripts
    └── script$cdpath/to/project-name.py
$exportSETUP_VERSION="1.0.0"$python-msetuppy_generator>setup.pysetup(name='project-name',version='1.0.0',classifiers=[...],long_description=open('README.md').read(),long_description_content_type='text/markdown',install_requires=['req1','req2'],packages=['pkgname'],py_modules=['module'],scripts=['scripts/script'])example #2 - environment variables$exportSETUP_URL="https://github.com/owner/repo"$exportSETUP_CLASSIFIERS="classifiers.txt"$exportSETUP_DESCRIPTION="description ..."$exportSETUP_KEYWORDS="key1 key2"$exportSETUP_LONG_DESCRIPTION="README.md"$exportSETUP_INSTALL_REQUIRES="requirements.txt"$exportSETUP_PACKAGES="package1 package2"$exportSETUP_PY_MODULES="module1 module2"$exportSETUP_SCRIPTS="scripts/script1 scripts/script2"$python-msetuppy_generator>setup.pysetup(name='project-name',version='1.0.0',url='https://github.com/owner/repo',classifiers=[...],description='description ...',long_description=open('README.md').read(),long_description_content_type='text/markdown',keywords='key1 key2',install_requires=['req1','req2'],packages=['package1','package2'],py_modules=['module1','module2'],scripts=['scripts/script1','scripts/script2'])open(path).read()function:$exportSETUP_VERSION="open('.config/version.txt').read().split()"$exportSETUP_DESCRIPTION="open('.config/description.txt').read().split()"$exportSETUP_KEYWORDS="open('.config/keywords.txt').read().split(' ')"$python-msetuppy_generator>setup.pysetup(...version=open('.config/version.txt').read().split(),description=open('.config/description.txt').read().split(),keywords=open('.config/keywords.txt').read().split(' '),...)example #3 - minimalsetup.py$exportSETUP_CLASSIFIERS=""$exportSETUP_DESCRIPTION=""$exportSETUP_KEYWORDS=""$exportSETUP_LONG_DESCRIPTION=""$exportSETUP_URL=""$python-msetuppy_generator>setup.pysetup(name='project-name',version='1.0.0',install_requires=['req1','req2'],packages=['pkgname'],py_modules=['module'],scripts=['scripts/script'])Relatedsetupcfg-generator-setup.cfggeneratorreadme42.com
Package: setup-python-package
A python package that helps you create a python package.How do I install this package?As usual, just download it using pip:pipinstallsetup_python_packageTests CoverageSince some software handling coverages sometime get
slightly different results, here’s three of them:RequirementsYou will need to have install the travis gem for encryption:geminstalltravisUsage exampleIn your terminal, from within a valid repository, just run the following:sppThe just follow the istructions, that go something like this
(this is taken directly from the setup of another repo o’ mine):Pleaseinsertpackagename[dict_hash]:Pleaseinsertauthorname[LucaCappelletti]:Pleaseinsertauthoremail[cappelletti.luca94@my.email.com]:Pleaseinsertpackageurl[https://github.com/LucaCappelletti94/dict_hash]:Pleaseinsertpackagedescription[Simplepythontooltohashdictionariesusingbothdefaulthashandsha256.]:Pleaseinsertpackageversion[1.0.0]:Pleaseinserttestsdirectory[tests]:Youmightneedtocreatethetravisproject.Pressentertogototravisnow.Youmightneedtocreatethesonarcloudproject.Justcopytheprojectkeyandpasteithere.Pressentertogotosonarnow.Pleaseinsertsonarprojectkey:(sonarkeygoeshere,removedforprivacy)Pleaserunthefollowingintoaterminalwindowinthisrepository:travisencrypt(sonarkeygoeshere,removedforprivacy)Copyonlythegeneratekeyhere,itlookslikethis:secure:"very_long_key"Pleaseinserttravisprojectkey:(traviskeygoeshere,removedforprivacy)Pleaseinsertpythonversion[3.7]:Youstillneedtocreatethecoverallsproject.Justcopytherepo_tokenandpasteithere.Pressentertogotocoverallsnow.
Package: setup-py-upgrade
setup-py-upgradeupgrade a setup.py to declarative metadatainstallationpipinstallsetup-py-upgradecliConsult the help for the latest usage:$setup-py-upgrade--helpusage: setup-py-upgrade [-h] directorypositional arguments:directoryoptional arguments:-h, --help  show this help message and exitpass the root directory of the repository you'd like to convertthe script overwritessetup.pyandsetup.cfgwhen runsample output$setup-py-upgrade../pre-commit../pre-commit/setup.py and ../pre-commit/setup.cfg written!$tail-n999../pre-commit/setup.{py,cfg}==> ../pre-commit/setup.py <==from setuptools import setupsetup()==> ../pre-commit/setup.cfg <==[metadata]name = pre_commitdescription = A framework for managing and maintaining multi-language pre-commit hooks.long_description = file: README.mdlong_description_content_type = text/markdownurl = https://github.com/pre-commit/pre-commitversion = 1.14.2author = Anthony Sottileauthor_email = asottile@umich.educlassifiers =License :: OSI Approved :: MIT LicenseProgramming Language :: Python :: 2Programming Language :: Python :: 2.7Programming Language :: Python :: 3Programming Language :: Python :: 3.6Programming Language :: Python :: 3.7Programming Language :: Python :: Implementation :: CPythonProgramming Language :: Python :: Implementation :: PyPy[options]packages = find:install_requires =aspy.yamlcfgv>=1.4.0identify>=1.0.0importlib-metadatanodeenv>=0.11.1pyyamlsixtomlvirtualenvfutures; python_version<"3.2"importlib-resources; python_version<"3.7"[options.packages.find]exclude =tests*testing*[options.entry_points]console_scripts =pre-commit = pre_commit.main:mainpre-commit-validate-config = pre_commit.clientlib:validate_config_mainpre-commit-validate-manifest = pre_commit.clientlib:validate_manifest_main[options.package_data]pre_commit.resources =*.tar.gzempty_template_*hook-tmpl[bdist_wheel]universal = Truewhat versions of setuptools / pip does the output work with?pip>=1.5(when installing from a wheel)released 2014-01-02setuptools>=30.3(when building from source)released 2016-12-08virtualenv>=15.2(to get a sufficient setuptools via--no-download)released 2018-03-21what is not supporteddeclarative metadata does not supportext_modulesor setuptools plugins --
those must stay insetup.py.  If you're converting a project which uses one
of those, you'll see a message like:$setup-py-upgrade../future-breakpoint/ext_modules= is not supported in setup.cfgTo convert those, temporarily remove the offending constructs fromsetup.py,
then runsetup-py-upgrade, then paste them back into the file.related projectssetup-cfg-fmt: apply a consistent format tosetup.cfgfiles
Package: setup_qt
Compile Qt resource files, UI files and translations in setup.pyCan be used with PyQt4, PyQt5, PySide and PySide2. Usage of Qt bindings
wrappers likeQt.pyorQtPyis also supported.RequirementsPython >= 3.4Setuptools (https://github.com/pypa/setuptools)PyQt4 / PyQt5 / PySide / PySide2Examplesetup.py:fromsetuptoolsimportsetupfromsetup_qtimportbuild_qtsetup(name='example',version='1.0.0',description='setup_qt example',author='Monty Python',author_email='monty.python@example.com',url='https://www.example.com',license='MIT',packages=['example'],package_data={'example':['*.ui','*.qrc','languages/*.ts','languages/*.qm',],},entry_points={'gui_scripts':['example=example.__main__:main',],},install_requires=['PyQt5','Qt.py',],options=['build_qt':{'packages':['example'],'languages':['cs'],# optional'languages_dir':'languages',# optional ('languages' is default)'bindings':'PyQt5',# optional ('PyQt5' is default)'replacement_bindings':'Qt',# optional (for Qt.py wrapper usage)},],cmdclass={'build_qt':build_qt,},)Usage:[user@host ~]$ python setup.py build_qt
running build_qt
compiling example Qt resource files...
compiling example Qt UI files...
updating example Qt translation files...
compiling example Qt translation files...HelpOptions for 'build_qt' command:
  --packages              List of comma separated packages in which to
                          recursively find .qrc, .ui and .ts files
  --languages             List of comma separated translation languages (could
                          be empty)
  --languages-dir         Directory with translation files (could be empty,
                          default is "languages")
  --bindings              Qt binding from which to use pyrcc, pyuic and
                          pylupdate commands (default is PyQt5)
  --replacement-bindings  Qt bindings replacement (e.g. if using wrapper like
                          Qt.py or QtPy)
  --pyrcc                 pyrcc command executable
  --pyuic                 pyuic command executable
  --pylupdate             pylupdate command executable
  --lrelease              lrelease command executable
  --filename-qrc          name template for .py files compiled from .qrc files
  --filename-ui           name template for .py files compiled from .ui files
  --filename-ts           name template for newly created .ts files
Package: setupreader
setup.py contains a function named setup.When writing software that works with python packages it is very
inconvenient to retrieve the package metadata from setup.py. This package
makes it easy, just point it at setup.py and get a dict.>>> import setupreader, json
>>> foo = setupreader.load('setup.py')
>>> print json.dumps(foo, indent=4)
{
    "description": "retrieve package specification from setup,py",
    "install_requires": [
        "setuptools",
        "mock"
    ],
    "zip_safe": false,
    "keywords": "",
    "packages": [],
    "classifiers": [],
    "entry_points": {
        "console_scripts": [
            "read-setup = setupreader:main"
        ]
    },
    "name": "setupreader",
    "license": "",
    "author": "Lars van de Kerkhof",
    "url": "",
    "include_package_data": true,
    "py_modules": [
        "setupreader"
    ],
    "long_description": "",
    "author_email": "lars@permanentmarkers.nl",
    "version": "0.0.1"
}
Package: setup-recipe
Runs thesetup.pyin all specified directories, using custom interpreter, e.g. the one generated by zc.buildout.egg
recipe. Its intended to be used to run any commands that require libraries (eggs) from buildout.
Any additional command line arguments are passed to thesetup.py. Setup is always run in working directory where it
resides.Parametersdevelop - List of directories, wheresetup.pyfile reside. Typically${buildout:develop}to list all developed apps.use-interpreter - Name of python interpreter to use. Optional, when not specified, system interpreter is used.command - Command line argument for thesetup.py. Optional.Typical buildout.cfg snippet:[python]
recipe = zc.recipe.egg
interpreter = python
eggs = ${buildout:eggs}

[test]
recipe = setup-recipe
use-interpreter = ${python:interpreter}
develop = ${buildout:develop}
command = testRunning./bin/testwill then run./bin/python setup.py testfor every developed project.Adding arguments./bin/test sdist register uploadwill then test, build and publish all apps to cheeseshop.
Since you can omit implicit command, you can have generic scriptsetupand call it with whatever arguments you wish.
Package: setup-requirements
A PEP 517 build backend that automatically addsrequirements.txtcontents to wheel dependencies.UsageUsesetup_requirementsas your build backend inpyproject.toml:[build-system]
requires = ['setuptools>=42', 'wheel', 'setup-requirements']
build-backend = 'setup_requirements'NotesThis backend should be used if you want to build anapplicationwith pinned dependencies. For libraries use standardinstall_requireswithout pins.The backend exists only because it’s not possible to usefile:ininstall_requires(yet?). See thisgithub issue.LimitationsIt’s not possible to use a different path than a top-levelrequirements.txtfile.
Package: setup-selenium-testing
setup-selenium-testingI get tired of having to rewrite the setup logic for selenium drivers
in every project.  Time to consolidate.Basic usagefromsetup_seleniumimportBrowser,SetupSeleniumdriver=SetupSelenium.create_driver(browser=Browser.CHROME,headless=True)Advanced usagefromsetup_seleniumimportBrowser,SetupSeleniumdriver=SetupSelenium.create_driver(browser=Browser.CHROME,headless=True,enable_log_performance=False,enable_log_console=False,enable_log_driver=False,log_dir="./logs",binary="/usr/bin/chromium",driver_path="/usr/bin/chromedriver",)[!NOTE]
It is possible to enable the performance and console logging
but only for chrome based browsers. This only enables the browser ability.
It is up to the tester to handle logging the messages.Driver installationfromsetup_seleniumimportBrowser,SetupSeleniumdriver_path,browser_path=SetupSelenium.install_driver(Browser.CHROME,"118.0.5993.70")Custom loggerimportloggingfromsetup_seleniumimportBrowser,SetupSelenium,set_loggerset_logger(logging.getLogger("your_custom_logger"))driver=SetupSelenium.create_driver(browser=Browser.CHROME,headless=True)Instantiating SetupSeleniumWhile it is possible to use the class directly caution is advised; as the class
will create the driver upon instantiation.fromsetup_seleniumimportSetupSeleniums=SetupSelenium(headless=True)asserts.driver.service.is_connectable()Automatic driver and browser installationThis package not only handles setup of the webdriver but also will
automatically install the webdriver and/or browser depending on your
configuration.If you do not provide adriver_pathargument tocreate_driverthe package
will utilizeselenium-managerto install the webdriver for the browser type selected.If theselenium-managercannot find the install path for the browser type
(which is usually in the native install path) it will download a version of the browser
and use that.Passing a validbinary_pathwill not trigger any download of the browser.
Passing a validdriver_pathwill not trigger any download of the webdriver.
Package: setup-teardown
Setup Teardown Content DecoratorThis is a simple package that aims to make adding setup and teardown to pytest flavored tests quick and painless.Installationpython3 -m pip install setup-teardownProvided Postgres Database Class Decorator UsageExtend and implement the session.class TableScrub(PostgresScrub):
    """Extend to add session."""

    @cached_property
    def session(self):
        """Only fetch the session one time."""
        return new_session()Example class with decorator usageclass TestHandlerDatabaseRequired:
    @TableScrub(table="table_name")
    def test_handler_success(self, mock_datetime):
        """
        Example of using the SetupTeardown ContextDecorator
        with arbitrary setup and teardown.
        """
        assert 1 == 1
        # Effect the database test that may leave db in dirty stateExample function with decorator usage@TableScrub(table="table_name")
    def test_insert():
        with TableScrub(setup=setup, teardown=teardown):
            assert 1 == 1
            # Effect the database test that may leave db in dirty stateExample function with context manager usagedef setup(self):
        db.session.new_session().query(self.table).delete()

    def teardown(self):
        db.session.new_session().query(self.table).delete()


    def test_insert():
        with SetupTeardown(setup=setup, teardown=teardown):
            assert 1 == 1
            # Effect the database test that may leave db in dirty state
Package: setuptestx
The ‘setuptetx‘ package provides an easy to use regression test interface for all supported platforms.The current supported implementations are:CPythonIPythonIronPythonJythonPyPyThe current supported platforms are:Linux, BSD, Unix, OS-X, Cygwin, and Windowsx86, amd64, arm32/armhf, arm64/aarch64Servers, Workstations, Embedded SystemsDatacenters, public and private Clouds, IoTFor more extensions refer to the online documentation.Online documentation:https://setuptestx.sourceforge.io/Runtime-Repository:PyPI:https://pypi.org/project/setuptestx/Install:pip install setuplib, see also section ‘Install’ of the online documentation.Downloads:sourceforge.net:https://sourceforge.net/projects/setuptestx/files/bitbucket.org:https://bitbucket.org/acue/setuptestxgithub.com:https://github.com/ArnoCan/setuptestx/pypi.org:https://pypi.org/project/setuptestx/Project DataPROJECT: ‘setuptestx’MISSION: Command extension ofsetup.pyfor multi-platform regression tests.VERSION: 00.01RELEASE: 00.01.046STATUS: alphaAUTHOR: Arno-Can UestuensoezCOPYRIGHT: Copyright (C) 2019 Arno-Can Uestuensoez @Ingenieurbuero Arno-Can UestuensoezLICENSE: Artistic-License-2.0 + Forced-Fairplay-ConstraintsConcepts and enumeration values are migrated from theUnifiedSessionsManager(C) 2008 Arno-Can Uestuensoez @Ingenieurbuero Arno-Can Uestuensoez.Runtime EnvironmentFor a comprehensive list refer to the documentation.Python Syntax SupportPython2.7, and Python3Python Implementation SupportCPython, IPython, IronPython, Jython, and PyPyOS on Server, Workstation, Laptops, Virtual Machines, and ContainersLinux: AlpineLinux, ArchLinux, CentOS, Debian, Fedora, Gentoo, OpenSUSE, Raspbian, RHEL, Slackware, SLES, Ubuntu, …BSD: DragonFlyBSD, FreeBSD, NetBSD, OpenBSD, GhostBSD, TrueOS, NomadBSDOS-X: Snow LeopardWindows: Win10, Win8.1, Win7, WinXP, Win2019, Win2016, Win2012, Win2008, Win2000WSL-1.0: Alpine, Debian, KaliLinux, openSUSE, SLES, UbuntuCygwinUNIX: Solaris10, Solaris11Minix: Minix3ReactOSNetwork and SecurityNetwork Devices: OpenWRTSecurity: KaliLinux, pfSenseOS on Embedded DevicesRaspberryPI: ArchLinux, CentOS, OpenBSD, OpenWRT, RaspbianASUS-TinkerBoard: ArmbianCreation of Special Deployment PackagesMicroPython: CircuitPython, MicroPythonCurrent ReleaseREMARK:Currently tested by application to the other projects of the author.
So for now no package tests defined.Major Changes:Initial version.ToDo:Deployment to remote MicroPython, and CircuitPython
Package: setuptools
See theQuickstartand theUser’s Guidefor
instructions on how to use Setuptools.Questions and comments should be directed toGitHub Discussions.
Bug reports and especially tested patches may be
submitted directly to thebug tracker.Code of ConductEveryone interacting in the setuptools project’s codebases, issue trackers,
chat rooms, and fora is expected to follow thePSF Code of Conduct.For EnterpriseAvailable as part of the Tidelift Subscription.Setuptools and the maintainers of thousands of other packages are working with Tidelift to deliver one enterprise subscription that covers all of the open source you use.Learn more.
Package: setuptools_bin_targets
Distutils/Setuptools provides a fantastic cross platform framework for
building python packages, including binary extensions using your platforms
standard c/c++ compiler.Why should it be limited only to use on python pyd extensions however,
there’s nothing to stop it being used for compiling anything with said comiler,
such as executables and static libraries.Well it turns out all the functionality is already there, it just isn’t really
exposed to the end user very easily. This is easily rectified however:from setuptools import setup
from ext_targets import build_ext, StaticLib, Executable


setup(
    name='binaries!',  # This isn't actually used in the built targets
    cmdclass={'build_ext': build_ext},
    ext_modules=ext_modules = [
        StaticLib(
            name='saveforlater',
            sources=['lib.c', 'required.c'],
            include_dirs=['../include']
        ),
        Executable(
            name='my_program',
            sources=['source.c', 'extra.cpp'],
            libraries=['libsaveforlater']
            language='c++',
            include_dirs=['../include'],
            extra_compile_args=['-static'],
            extra_link_args=['-static']
        )
    ]
)
Package: setuptools-black
Custom setuptools command for black formatting tool (seehttps://github.com/ambv/black).This package adds theformatcommand to setuptools, which uses black to reformat code:>pythonsetup.pyformat
runningformat
Alldone!✨🍰✨5filesleftunchangedYou may also use customize thebuildcommand to enforce format validation at build time.
Build will fail if there's any formatting error.In your setup.py:importsetuptools_black...setuptools.setup(...cmdclass={"build":setuptools_black.BuildCommand,},...)NoteYou'll have to install setuptools-black first, as setup_requires can't be used to install a package which must be imported by setup.py itself...
Package: setuptools-bower
Aboutsetuptools-bower provides setuptools commands for integrating bower.Usagesetuptools-bower is on PyPI so all you need is:pip install setuptools-bowerThen from within your Python package, you can now run:python setup.py install_bowerThis will run`bower install`in the directory and is thus expecting to find a`bower.json`and respect any configuration in a`.bowerrc`file.In your`setup.cfg`you may setup aliases to combine bower installation with your normal install:[aliases]
install_all = install_bower installDocumentationDocumentation is readable athttp://setuptools-bower.readthedocs.orgor can be build using Sphinx:git submodule init
git submodule update
pip install Sphinx
python setup.py build_sphinxTestingRunning the test suite is as simple as:python setup.py testor, to also show test coverage:source run-coverage.shLicenseCopyright (C) 2013, 2014 CERN.setuptools-bower is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.setuptools-bower is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License for more details.You should have received a copy of the GNU General Public License along with setuptools-bower; if not, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307, USA.In applying this licence, CERN does not waive the privileges and immunities granted to it by virtue of its status as an Intergovernmental Organization or submit itself to any jurisdiction.