tox-extra
This tox plugin adds a few extra checks like:
Checks Git Dirty Status
It ensures exit code 1 if git reports dirty or untracked files after the run.
Usage example:
$ tox -e py
...
ERROR: Git reported dirty status. Git should never report dirty status at the end of testing, regardless if status is passed, failed or aborted.
On branch devel
Your branch is up to date with 'origin/devel'.
Untracked files:
(use "git add <file>..." to include in what will be committed)
some-untracked.txt
nothing added to commit but untracked files present (use "git add" to track)
__________________________________________ summary ___________________________________________
ERROR: py: failed
The goal of this plugin is to help developers be aware of files modified by tests
or untracked files before they commit the code. This plugin also does not take into
consideration the global .gitignore, something that can make git miss reporting
some untracked files, the goal being to assure that when a new developer clones and
runs the tests they do not endup with an unexpected git status.
If you have any cases where you expect to have git report dirty, please
add --allow-dirty to the command call to disable this check.
Checks system dependencies using bindep
If a bindep.txt config file is found, tox will run bindep [profiles] to
check if dependencies, including test ones, are present. There is no need to
install bindep your self.
This plugin will add the following list of bindep profiles:
testis always added as tox itself is a test tool- exact tox env name
- tox env name itself split by `-'
pythonX.YandpyXYbased on which python current tox env will use
This should allow developers to modify their bindep.txt file to include
system dependencies specific to a single tox environment if they wish.
To disable bindep feature, you can define TOX_EXTRA_BINDEP=0 in your
environment.
Improves colored output on CI
Multiple tools, including tox and pre-commit fail to property use coloring when run in a CI evironment like Github Actions. This plugin will inject additional environment variables in order to ensure that the tool output remains colored.
It should be noted that this happens only if these variables are not already defined by the user. This feature should reduce the need of adding extra environment variables to your pipelines.
Release files for tox-extra 2.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| tox_extra-2.2.0.tar.gz | 16.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| tox_extra-2.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 24.5 kB
Release files / tox_extra-2.2.0.tar.gz
| Download URL | tox_extra-2.2.0.tar.gz |
|---|---|
| Size | 16.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
38966d94d11965658df74b78d1aafc3abff6b155a41e51577a479babc1777a78
|
|
BLAKE2b-256 checksum How to use checksums |
fefa2436ebe93ce6f25247d0e25e77c3f7af6eb9e18b700d3e76b111bc12b65a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 25, 2025.
Transparency logRelease files / tox_extra-2.2.0-py3-none-any.whl
| Download URL | tox_extra-2.2.0-py3-none-any.whl |
|---|---|
| Size | 7.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ba3745c2d4d6d3efa2e49d9138e304af1ac261907e13cbaf987ec73bdad11a46
|
|
BLAKE2b-256 checksum How to use checksums |
a53092cba6121b67b8c0c702f1d8873312fe6dbbb223ef9e00d1e0acb48cbbc5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 25, 2025.
Transparency log