| 1 |
Source: tox |
| 2 |
Section: python |
| 3 |
Maintainer: Debian Python Team <[email protected]> |
| 4 |
Uploaders: Faidon Liambotis <[email protected]> |
| 5 |
Homepage: https://tox.wiki/ |
| 6 |
Build-Depends: |
| 7 |
debhelper-compat (= 13), |
| 8 |
dh-python, |
| 9 |
dh-sequence-python3, |
| 10 |
pybuild-plugin-pyproject, |
| 11 |
python3-all, |
| 12 |
python3-cachetools, |
| 13 |
python3-colorama, |
| 14 |
python3-docutils, |
| 15 |
python3-filelock, |
| 16 |
python3-packaging (>= 26.0-1~), |
| 17 |
python3-platformdirs, |
| 18 |
python3-pyproject-api, |
| 19 |
python3-discovery (>= 1.2.1), |
| 20 |
python3-virtualenv, |
| 21 |
python3-hatchling, |
| 22 |
python3-hatch-vcs, |
| 23 |
dh-doc-privacy <!nodoc>, |
| 24 |
dh-sequence-sphinxdoc <!nodoc>, |
| 25 |
libjs-d3 <!nodoc>, |
| 26 |
python3-doc <!nodoc>, |
| 27 |
python3-sphinx <!nodoc>, |
| 28 |
python3-sphinx-argparse-cli <!nodoc>, |
| 29 |
python3-sphinx-autodoc-typehints <!nodoc>, |
| 30 |
python3-sphinxcontrib-mermaid <!nodoc>, |
| 31 |
python3-sphinxcontrib-towncrier <!nodoc>, |
| 32 |
python3-sphinx-copybutton <!nodoc>, |
| 33 |
python3-sphinx-inline-tabs <!nodoc>, |
| 34 |
python3-sphinx-issues <!nodoc>, |
| 35 |
python3-sphinx-reredirects <!nodoc>, |
| 36 |
python3-truststore <!nodoc>, |
| 37 |
furo <!nodoc>, |
| 38 |
Standards-Version: 4.7.4 |
| 39 |
Vcs-Git: https://salsa.debian.org/python-team/packages/tox.git |
| 40 |
Vcs-Browser: https://salsa.debian.org/python-team/packages/tox |
| 41 |
|
| 42 |
Package: tox |
| 43 |
Architecture: all |
| 44 |
Depends: |
| 45 |
python3, |
| 46 |
${misc:Depends}, |
| 47 |
${python3:Depends}, |
| 48 |
Recommends: |
| 49 |
${sphinxdoc:Depends}, |
| 50 |
libjs-d3, |
| 51 |
Built-Using: |
| 52 |
${sphinxdoc:Built-Using} |
| 53 |
Description: virtualenv-based automation of test activities |
| 54 |
Tox as is a generic virtualenv management and test command line tool |
| 55 |
you can use for: |
| 56 |
. |
| 57 |
* checking your package installs correctly with different Python |
| 58 |
versions and interpreters |
| 59 |
* running your tests in each of the environments, configuring your |
| 60 |
test tool of choice |
| 61 |
* acting as a frontend to Continuous Integration servers, greatly |
| 62 |
reducing boilerplate and merging CI and shell-based testing. |