Reason: Test automation tools. They are generally used to run the test suite across multiple Python versions, i.e. what our eclasses do for you already. They usually can't work inside network sandbox (since they fetch and install all the dependencies inside the venv), so even if they are listed in dependencies, your package probably does not actually need them to run tests.
Deprecated by Michał Górny on 2022-06-19
Install this package:
emerge -a dev-python/tox
| Version | EAPI | Keywords | Slot |
|---|---|---|---|
| 4.61.4 | 8 | ~alpha ~amd64 ~arm ~arm64 ~hppa ~m68k ~ppc ~ppc64 ~riscv ~s390 ~x86 | 0 |
| 4.61.3 | 8 | ~alpha ~amd64 ~arm ~arm64 ~hppa ~m68k ~ppc ~ppc64 ~riscv ~s390 ~x86 | 0 |
| 4.61.2 | 8 | ~alpha ~amd64 ~arm ~arm64 ~hppa ~m68k ~ppc ~ppc64 ~riscv ~s390 ~x86 | 0 |
| 4.61.1 | 8 | ~alpha ~amd64 ~arm ~arm64 ~hppa ~m68k ~ppc ~ppc64 ~riscv ~s390 ~x86 | 0 |
| 4.60.1 | 8 | ~alpha ~amd64 ~arm ~arm64 ~hppa ~m68k ~ppc ~ppc64 ~riscv ~s390 ~x86 | 0 |
| 4.58.0 | 8 | ~alpha amd64 arm arm64 ~hppa ~m68k ppc ppc64 ~riscv ~s390 x86 | 0 |
<pkgmetadata> <maintainer type="project"> <email>python@gentoo.org</email> <name>Python</name> </maintainer> <stabilize-allarches></stabilize-allarches> <upstream> <remote-id type="pypi">tox</remote-id> <remote-id type="github">tox-dev/tox</remote-id> </upstream> </pkgmetadata>
| Type | File | Size | Versions |
|---|
| Type | File | Size |
|---|---|---|
| DIST | tox-4.58.0.tar.gz | 296926 bytes |
| DIST | tox-4.58.0.tar.gz.provenance | 9487 bytes |
| DIST | tox-4.60.1.tar.gz | 303833 bytes |
| DIST | tox-4.60.1.tar.gz.provenance | 9485 bytes |
| DIST | tox-4.61.1.tar.gz | 306574 bytes |
| DIST | tox-4.61.1.tar.gz.provenance | 9313 bytes |
| DIST | tox-4.61.2.tar.gz | 306825 bytes |
| DIST | tox-4.61.2.tar.gz.provenance | 9818 bytes |
| DIST | tox-4.61.3.tar.gz | 307979 bytes |
| DIST | tox-4.61.3.tar.gz.provenance | 9438 bytes |
| DIST | tox-4.61.4.tar.gz | 308140 bytes |
| DIST | tox-4.61.4.tar.gz.provenance | 9548 bytes |