Saravanan666/pypi-org huggingface dataset:
Package: tox-ltt
packagecodeteststoxplugin forlight-the-torch.$pipinstalltoxtox-ltt$tox--help-inidisable_light_the_torch<bool>default:FalsedisableinstallingPyTorchdistributionswithlight-the-torchforce_cpu<bool>default:FalseforceCPUascomputationbackend[...]NoteIf you have access totox>=3.2you can usetox-lttwith therequireskeyword:[tox]
requires =
  tox-ltt

[textenv]
disable_light_the_torch = False
force_cpu = False
Package: tox-matrix
Project for creating tox.ini files with multiple dependencies.Free software: BSD licenseDocumentation:http://tox-matrix.rtfd.org.A little utility script to generatetox.inifiles.
It should be handy in case where your project have multiple different dependencies
with different version and you would like to test all available configurations of them.Quick startInstall it:pip install tox-matrixNow let’s assume you’d like to test your project against different versions
ofDjango(latest 1.5.X and 1.6.X ) andFabric(latest 1.7.X and 1.8.X)
usingpython2.7andpython3.3.
You could do something like this:tox-matrix generate -d Django -v 1.5,1.6,1.7 -d Fabric -v 1.7,1.8,1.9 -p 2.7 -p 3.3Which should generate thistox.inifile content to stdout:[tox]
envlist = py27-A, py27-B, py27-C, py27-D, py33-A, py33-B, py33-C, py33-D

[testenv]
commands = py.test

[testenv:py27-A]
basepython = python2.7
deps = {[testenv]deps}
    Django>=1.5,<1.6
    Fabric>=1.7,<1.8

[testenv:py27-B]
basepython = python2.7
deps = {[testenv]deps}
    Django>=1.5,<1.6
    Fabric>=1.8,<1.9

[testenv:py27-C]
basepython = python2.7
deps = {[testenv]deps}
    Django>=1.6,<1.7
    Fabric>=1.7,<1.8

[testenv:py27-D]
basepython = python2.7
deps = {[testenv]deps}
    Django>=1.6,<1.7
    Fabric>=1.8,<1.9

[testenv:py33-A]
basepython = python3.3
deps = {[testenv]deps}
    Django>=1.5,<1.6
    Fabric>=1.7,<1.8

[testenv:py33-B]
basepython = python3.3
deps = {[testenv]deps}
    Django>=1.5,<1.6
    Fabric>=1.8,<1.9

[testenv:py33-C]
basepython = python3.3
deps = {[testenv]deps}
    Django>=1.6,<1.7
    Fabric>=1.7,<1.8

[testenv:py33-D]
basepython = python3.3
deps = {[testenv]deps}
    Django>=1.6,<1.7
    Fabric>=1.8,<1.9FeaturesGenerate tox.ini filesPin versions either with exact ones or by rangeUse a Jinja2 template for your tox.ini fileHistory0.1.1 (2014-03-26)Fixes for installation and tests0.1.0 (2014-03-23)First release on PyPI.
Package: tox-min-req
tox-min-reqTable of ContentsInstallationLicenseUsagetox-min-req is atoxplugin that simplify the
minimum requirements testing.The minimum requirements is to validate if minimum requirements are
satisfied.To use this plugin you need to useMIN_REQenvironment variable either in call or insetenvsection
of tox configuration.Why use this inseted ofdepsattribute of env section?One of the possible solution is to usedepssection in tox configuration to install dependecies in older version.Butdepsand package are installed in two independent steps. So it means that
some of dependencies could be upgraded or downgraded when installing package.ThePIP_CONSTRAINTvariable is used to pin the dependencies. And it will apply to call ofpip installduring dependency resolving.Installationpip install tox-min-reqLicensetox-min-reqis distributed under the terms of theMITlicense.UsageThe basic usage is to set theMIN_REQenvironment variable to1$MIN_REQ=1tox-epy37Configuration optionsThetox-min-reqplugin allow to provide following environment configuration options:min_req- set to1to enable the minimum requirements testing, could be used instead of environment variable.min_req_constraints- list of additional constrains that will be used to generate the constrains file.
It could be useful in following scenarios:Some of dependencies in old version is incompatible with its dependencies in latest version. (see Known issues)Maintainers would like to test also some problematic dependencies in old version, but not oldest supported version.[tox]envlist=py310[testenv]extras=testrecreate=Truecommands=pytest test_file.pymin_req=1min_req_constraints=coverage==6.5.0babel==2.6.0six==1.14.0-r {project_dir}/constraints.txtPlease note that-r {project_dir}/constraints.txtwill be put in generated constrains file, not parsed.Known issuesPinning only direct dependenciesAs this plugin parse onlysetup.cfgorpyproject.tomlfile, it is not possible to pin the indirect dependencies.
To provide the indirect dependencies pinning, themin_req_constraintsenvironment configuration option could be used.Space in constrains file pathpipis using the space as file path separator inPIP_CONSTRAINTvariable.
The plugin is storing the generated constrains file in the.toxtemporary directory.
If the path to the temporary directory contains space, thepipwill not be able to find the constrains file.In such situation there is a need to set theTOX_MIN_REQ_CONSTRAINTSenvironment variable
to the path where constrains file could be written.$TOX_MIN_REQ_CONSTRAINTS=/tmpMIN_REQ=1tox-epy37It is also possible to use the--min-req-constraints-pathcommand line option to set the path to the constrains file.$tox--min-req-constraints-path=/tmp-epy37
Package: tox-monorepo
tox-monorepoThis plugin changes {toxinidir} to be the directory that executes the tox command, rather than where the tox.ini actually lives on disk. This allows a monorepo to easily share a single tox.ini file rather than have to keep copies up to date.FeaturesOnce installed,tox-monorepowill actively post-process the loadedtox configand replace all instances of{toxinidir}with a reference to thecurrent working directory.Note that if there are any out-of-ordinary changes present within your tox config, it is highly likely that this plugin has not been tested with them. ReferenceContributingsection for how to reach out if issues crop up.RequirementsTested ontox 3.1+,Python 2.7+InstallationYou can install "tox-monorepo" viapipfromPyPI:pip install tox-monorepoUsageInstall the plugin, then try to reference a tox config from within a package directory.tox -c <otherpath>/to/tox.iniNote that all the.toxfolder + any environments are now createdrelative to the directory that executed tox.Complete Set of Updated Config ValuesBase Config Values:{toxinidir}
{toxworkdir}
{temp_dir}
{setupdir}
{distdir}
{sdistsrc}
{logdir}Env-Specific Config Values{commands}
{commands_pre}
{commands_post}
{envdir}
{changedir}
{envtmpdir}
{envlogdir}ContributingContributions are very welcome, though the plugin isextremelystraightforward and shouldn't really require updates. Just submit a PR or an Issue on the the current repo!LicenseDistributed under the terms of theMITlicense,tox-monorepois
free and open source software.IssuesIf you encounter any problems, pleasefile an issuealong withtox-monorepoin the title.
Package: tox-no-deps
tox-no-deps pluginThis plugin skips the installation of alldepsandextrasof all the
Tox environments. The dependencies of tested package if any are not touched.This is mostly used for testing purposes in ALTLinux during RPM build of Python
packages to run integration tests against the repository packages.UsageOnly the CLI option is supported, the configuration's one is considered
ambiguous.tox --no-depsLicenseDistributed under the terms of theMITlicense,tox-no-depsis
free and open source software.
Package: tox-nuitka
tox-nuitkaA tox plugin to replace the default use of the CPython compiler with nuitka.This plugin works by injecting Nuitka as a pip requirement to all test environments and then adding the Nuitka
compile as a pre-test stage.Installationpipinstalltox-nuitkaOr,pipenvinstalltox-nuitkaExecuting testsEach of the commands in your testenv configuration will be compiled by nuitka to execute within the pipenv virtual environmentExample tox.iniThis simple example will run pytest against your package but compile myapp/main.py using Nuitka.[tox]
envlist = py27, py36, py37

[testenv]
nuitka = myapp/main.py
deps = pytest
commands = python -m pytest test/Additional Nuitka configuration is available within the test environment settings.Currently, the –module and –recurse-all flags are available like this:nuitka_module = true
nuitka_recurse_all = trueMultiple compile targets can be providednuitka =
        myapp/target1.py
        myapp/target2.pyRelease notes1.0.0 (date)Feature
Package: tox-pdm
tox-pdmA plugin for tox that utilizes PDM as the package manager and installer.With this plugin, you can migrate your project to PDM while retaining the ability to test against multiple versions.Installation$pipinstalltox-pdmOr,$pdmadd-dtox-pdmOr if you installedtoxviapipx, you can inject the plugin by:$pipxinjecttoxtox-pdmExample tox.iniThe following simple example installsdevandtestdependencies into the venv created by Tox and uses pytest to execute the tests, on both Python 3.7 and 3.8.[tox]min_version=4.0envlist=py37,py38[testenv]groups=; Dependency groups in pyproject.tomldevtestdeps=; Additional dependencies, it will be installed into the library path via normal pip methodflake8commands=pytest test/Here is another one installing thetestdependencies and executing thetestPDM script[tox]min_version=4.0envlist=py3{8,9,10}[testenv]groups=testcommands=testIf no groups are specified, the pdm install will be skipped.A real-world example can be found at this repository'stox.iniandGitHub Action workflow.Some best practices:pdmexecutable must be exposed inPATH, if it is not the case, give the absolute path to tox bytox --pdm <path_to_pdm>.Make sure you have generatedpdm.lockbefore running the test, it will greatly accelerate the testing.If you don't setskip_install = true, the current package will be built and installed into the testing environment together with thedependenciesfrompyproject.toml.Reuse your PDM scripts to avoid duplication
Package: tox-pipenv-install
FeaturesTODOInstallationYou can install “tox-pipenv-install” viapipfromPyPI:$ pip install tox-pipenv-installUsageTODOContributingContributions are very welcome. Tests can be run withtox, please ensure
the coverage at least stays the same before you submit a pull request.LicenseDistributed under the terms of theMITlicense, “tox-pipenv-install” is free and open source softwareIssuesIf you encounter any problems, pleasefile an issuealong with a detailed description.
Package: tox-pip-extensions
tox-pip-extensionsAugment tox with different installation methods via progressive enhancement.Installationpip install tox-pip-extensionsSupported extensionsvenv-update (pip-faster)venv-update has the desirable behavior that it synchronizes the installed
packages to the dependencies you ask for and uninstalls extraneous things
quickly (without removing the virtualenv) -- you'll never needtox --recreateagain!To enable this enhancement, simply add:[tox]tox_pip_extensions_ext_venv_update=truepip-custom-platformpip-custom-platform is useful if you'd like to target other operating systems
and maintain an internal pypi server containing precompiled wheels.To enable this enhancement, simply add:[tox]tox_pip_extensions_ext_pip_custom_platform=truepip-custom-platform + venv-update (pip-faster)These extensions can be used together, simply add both:[tox]tox_pip_extensions_ext_venv_update=truetox_pip_extensions_ext_pip_custom_platform=trueBootstrap requirementsBy default,tox-pip-extensionswill intelligently choose what versions to
install based on the plugins selected.If you'd like to pin specific versions,tox-pip-extensionswill defer to a
file namedrequirements-bootstrap.txtin the same directory astox.ini.
Package: tox-pip-version
[![Build Status](https://travis-ci.com/pglass/tox-pip-version.svg?branch=master)](https://travis-ci.com/pglass/tox-pip-version)
![](https://img.shields.io/pypi/v/tox-pip-version.svg)
![](https://img.shields.io/pypi/pyversions/tox-pip-version.svg)OverviewThis is a tox plugin that preinstalls a specific version of pip in each tox
environment.`bash pip installtox-pip-version`This works around the default behavior of tox/virtualenv that always installs
the latest version pip. It is an improvment over theVIRTUALENV_NO_DOWNLOAD=1option that does not install the latest version, but could result in usage of
an outdated version of pip.Recommendation: Do not pin the pip version long term. You get more stable
repeatable builds, but at the cost of using an outdated (possibly vulnerable)
package. This should be used as a temporary fix for breakages in upstream pip,
or in conjunction with a regular process to update the version pin.Note: This relies on an [unstable tox plugin interface](https://tox.readthedocs.io/en/latest/plugins.html#tox.hookspecs.tox_testenv_create).
You may experience breakage with new tox versions. If you do, please feel
free to [report the issue](https://github.com/pglass/tox-pip-version/issues/new)
on Github.### UsageInstall the package and includepip_versionin your tox.ini`tox [testenv] pip_version =pip==19.0.1`Or, set theTOX_PIP_VERSIONenvironment variable,`bash export TOX_PIP_VERSION=18.1 tox `The plugin will install that version of pip into the tox-created virtualenv,
just after tox creates the virtualenv, but before dependencies are installed.Thepip_versionwithin tox.ini, if present, is always used over the
environment variable.If neitherpip_versionorTOX_PIP_VERSIONis present, the plugin does
nothing.### Version SetsVersion sets/ranges are supported, enabling installation of a version of pip
matching a set of specifiers. There are two basic formats: a plain version
number, or the package name with optional [PEP440-compatible](https://www.python.org/dev/peps/pep-0440/#version-specifiers) version
specifiers.tox.ini                      | effective pip command        |—————————- | —————————- |pip_version = 19.0|pip install -U pip==19.0|pip_version = pip==19.0|pip install -U pip==19.0|pip_version = pip>=19.0|pip install -U pip>=19.0|pip_version = pip!=19,>18|pip install -U pip!=19,>18|pip_version = pip|pip install -U pip|### TestsUsemake testto run the tests, which includes linting and functional tests.Each of thetests/*directories is a “feature” that needs testing. Each
feature sub-directory contains a tox.ini file that sets pip version in a
particular way, and then uses a tox command to check the correct pip version
was installed.
Package: tox-plus
What is Tox-plus?Tox-plus is a fork of tox done in order to add more features to it.![Build Status](https://travis-ci.org/Itxaka/tox-plus.svg?branch=master)DifferencesThe{env:key:default}substitution for commands now worksAdded 2 extra hooks for plugins,pretestandposttestexecuted before and after the tests are run, for easy and useful plugin developmentWhat is Tox?Tox is a generic virtualenv management and test command line tool you can use for:checking your package installs correctly with different Python versions and
interpretersrunning your tests in each of the environments, configuring your test tool of choiceacting as a frontend to Continuous Integration servers, greatly
reducing boilerplate and merging CI and shell-based testing.For more information and the repository please checkout:homepage:http://tox.testrun.orgrepository:https://bitbucket.org/hpk42/toxhave fun,holger krekel, 2015
Package: tox-poetry
tox-poetry:bangbang:tox-poetry is now deprecated, please follow the examples in theofficial poetry documentation.Usage:Install plugin:pipinstalltox-poetrytox.ini:[tox]envlist=py39[testenv]commands=pytest tests/Plugin installs all dependencies from pyproject.toml before running any commands.
Like simple toxdeps, poetry dependencies are installed only once when tox environment is created,
you can runtox -rto recreate environment.extrassupported too.Example pyproject.toml:[build-system]requires=["poetry>=1,<2"]build-backend="poetry.masonry.api"[tool.poetry]name="example-app"version="0.1.0"authors=[]description=""[tool.poetry.dependencies]django="*"[tool.poetry.dev-dependencies]pytest="*"Example output:py38 recreate: /src/.tox/py38
py38 installdeps: /poetry/bin/poetry install
py38 installed: atomicwrites @ file:///pypoetry/artifacts/ca/84/dd/000dbc2864acca52a74a82da8b597c9e4778eb3fe64687a31a8095ad5f/atomicwrites-1.4.0-py2.py3-none-any.whl,attrs @ file:///pypoetry/artifacts/b7/28/6f/acdd2c0e759f1cda97abf00db7723a0ffb3a151696d8d96398aea16171/attrs-20.3.0-py2.py3-none-any.whl,Django @ file:///pypoetry/artifacts/2c/92/a3/702031af33acac0ba5b8551e05589cc106b52f094520fc0b189974b826/Django-1.11.29-py2.py3-none-any.whl,more-itertools @ file:///pypoetry/artifacts/1e/40/b5/3004e210820ef8517710ed156fa6d8585a1358fd5caf4720f2425443f8/more_itertools-7.2.0-py3-none-any.whl,packaging @ file:///pypoetry/artifacts/09/cd/29/a435224f3203dfba4af491065632910aadb6f3ddd87ce3c6590ac29e7a/packaging-20.4-py2.py3-none-any.whl,pluggy @ file:///pypoetry/artifacts/9c/e5/0b/2d64d03361a081edeb5d2ec5f286ccf9719587781fbf6822e1b6384c27/pluggy-0.13.1-py2.py3-none-any.whl,py @ file:///pypoetry/artifacts/f5/51/7d/d8aec03f59299351465053794c7b1f0e0e7a918e4a67911664f83929af/py-1.9.0-py2.py3-none-any.whl,pyparsing @ file:///pypoetry/artifacts/da/e7/3d/1780282f558e5fd157bf708b28b8ba0d08323ef6bc5b6396139ce38a0b/pyparsing-2.4.7-py2.py3-none-any.whl,pytest @ file:///pypoetry/artifacts/2d/0c/37/bc460d960d868e47170715a52c3c0431b094579b27805bb40fd5fd7da3/pytest-4.6.11-py2.py3-none-any.whl,pytz @ file:///pypoetry/artifacts/7a/8e/a2/e796ae4d320aded38d3d61817b158184888dcd18c6a4f6d6ab011a6cda/pytz-2020.4-py2.py3-none-any.whl,six @ file:///pypoetry/artifacts/be/98/c7/69fe6fea7a59659af1c6260899226129565330b1e07c9c5b3769be76bf/six-1.15.0-py2.py3-none-any.whl,wcwidth @ file:///pypoetry/artifacts/36/68/e2/7232f431072d5e8aeec124120b9a1d095d45da10311d271fac10982473/wcwidth-0.2.5-py2.py3-none-any.whl
py38 run-test-pre: PYTHONHASHSEED='966757075'
py38 run-test: commands[0] | pytest tests
Package: tox-py
Unmaintained (2022-12-08)With the release of tox 4, this package is no longer necessary, and so is not being maintained.
You can instead use tox 4’s-foption - see below.Adds the--pyflag to tox to run environments matching a given Python interpreter.InstallationUsepip:python-mpipinstalltox-pyPython 3.7 to 3.11 supported.Only tox 3 is supported.On tox 4, you can use the new-ffactor optionto select environments by Python version:$tox-fpy310On GitHub Actions, you can use-fwith your matrix python version like so:jobs:tests:name:Python ${{ matrix.python-version }}strategy:matrix:python-version:-3.7-3.8-3.9-'3.10'-'3.11'steps:-...-name:Run tox targets for ${{ matrix.python-version }}run:tox run -f py$(echo ${{ matrix.python-version }} | tr -d .)Testing a Django project?Check out my bookSpeed Up Your Django Testswhich covers loads of ways to write faster, more accurate tests.UsageAfter installation, the plugin will be automatically picked up bytox.
It adds one argument:--py, which takes the version to filter environments against.
The version can be specified either as atox.ini-style dotless version number, or the special stringcurrentfor the version of Python thattoxis running under.For example, to run all Python 3.9 environments:tox--py39Or to run all environments matching the version of Python thattoxis running under:tox--pycurrentThis makes configuring CI really easy: configure your CI to trigger each Python version in parallel, runningtox--pycurrent.
Package: tox-pyenv
Plugin that tellstoxto
usepyenv whichtofind python
executablesYour project’scircle.ymlIn order fortoxto have the versions of python you want available,
set them usingpyenv localdependencies:override:-pip install tox tox-pyenv-pyenv local 2.7.9 3.4.3 3.5.0The versions passed topyenv localmust beinstalledfor this to work. SeeCircleCI Preinstalled Python
Versionsfor a list.Correspondingtox.ini[tox]envlist=py27,py34,py35The result of the setup above means runningtoxwill run tests
against python 2.7.9, python 3.4.3 and python 3.5.0, assuming those
versions of python have beenpyenv installed.notesIf you want tox toexclusivelyusepyenv whichto find
executables, you will need use the--tox-pyenv-no-fallbackcommand
line option, or settox_pyenv_fallback=Falsein your tox.ini. By
default, iftox-pyenvfails to find a python executable it will
fallback to tox’s built-in strategy.CircleCI Preinstalled Python VersionsHere is the list of python versions that arepre-installedin the
CircleCI build environment (as of 09/27/2017):$ pyenv versions
  system
  2.6.6
  2.6.8
  2.7
  2.7.10
  2.7.11
  2.7.3
  2.7.4
  2.7.5
  2.7.6
  2.7.7
  2.7.8
* 2.7.9 (set by /home/ubuntu/.pyenv/version)
  3.1.5
  3.2
  3.2.5
  3.3.0
  3.3.2
  3.3.3
  3.4.0
  3.4.1
  3.4.2
  3.4.3
  3.5.0
  pypy-2.2.1
  pypy-2.3.1
  pypy-2.4.0
  pypy-2.5.0If the version you need isn’t in the list, such as Python3.6-devinclude aninstallstep:dependencies:
  override:
    - pip install tox tox-pyenv
    - pyenv install --skip-existing 3.6-dev
    - pyenv local 3.6-dev
Package: tox-pyenv-redux
tox-pyenv-reduxAtoxPython discovery plugin forpyenv–installed interpretersCompatibilityFor legacy versions of tox (0.x—3.x), use tox-pyenv-redux 0.x (tox-pyenv-redux < 1). These versions do not rely onvirtualenv-pyenvandDO NOTsupport thepyenv_discoverysetting.For the current version of tox (4.x), use tox-pyenv-redux 1.x (tox-pyenv-redux >= 1, < 2). These versions delegate the discovery job tovirtualenv-pyenv.Installationpipinstalltox-pyenv-reduxUsageThe plugin is enabled by default and configured to use the default discoveryoperation mode. To change the mode or disable the plugin, set thepyenv_discoveryenvironment setting to one of the following values:One of theoperation modes(e.g.,fallback) to use the specific operation mode.pyenv_discovery = fallbackis equivalent toexport VIRTUALENV_DISCOVERY=pyenv-fallback.defaultto use the default operation mode. This is the default value.pyenv_discovery = default(or no setting) is equivalent toexport VIRTUALENV_DISCOVERY=pyenv.offto disable the plugin. The plugin will not touch theVIRTUALENV_DISCOVERYenvironment variable, but thevirtualenv-pyenvdiscovery can still be in effect if virtualenv is already configured to use it (via theVIRTUALENV_DISCOVERYenvironment variable or thediscoveryconfig setting).ExamplesSet thefallbackoperation mode via a config file:[tox]min_version=4.0requires=tox-pyenv-redux[testenv]pyenv_discovery=fallbackdeps=pytestcommands=pytest {posargs}Disable the plugin via command line arguments:toxrun-xtestenv.pyenv_discovery=off
Package: tox-pyo3
Build a rust extension using PyO3 using toxAn extremely basic plugin that builds Rust extensions within tox virtualenvs.FeaturesRuns maturin developRequirementsmaturin must be installed somewhere in your systemA rust compilerInstallationYou can install “tox-pyo3” viapipfromPyPI:$ pip install tox-pyo3UsageWhen you set pyo3=true in your testenv this plugin
automatically detects if Cargo.toml is present and if so, it will compile the
extensionExample:`ini [testenv] pyo3 = True `ContributingContributions are very welcome. Tests can be run withtox, please ensure
the coverage at least stays the same before you submit a pull request.LicenseDistributed under the terms of theBSD-3license, “tox-pyo3” is free and open source softwareIssuesIf you encounter any problems, pleasefile an issuealong with a detailed description.
Package: tox-pypi-filter
AboutTox includes a--force-depoption that can be used to provide version
restrictions for dependencies - however, by design this only works with
dependencies explicitly listed in thedepssection of thetox.inifile
(seethis issuefor a
discussion of this).Thetox-pypi-filterplugin works around this by using a proxy PyPI server
that filters packages in a way that is independent of tox’s implementation.InstallingTo install:pip install tox-pypi-filterUsingThis plugin provides a--pypi-filtercommand-line option that takesPEP440 version specifiersseparated by
semicolons, e.g.:tox --pypi-filter "numpy==1.14.*;pytest<4" -e py37-testIn this case, if Numpy or PyTest are needed by the tox environment, the versions
that will be installed will satisfy the version specification supplied.CaveatsThis plugin will not work properly if you use the-i/--index-urloption
manually when calling tox. In addition, this will only work with pip-based
installs, and will not work with e.g.tox-conda.