tox-ini-fmt
See the changelog for released changes. A user-facing pull request needs a
changelog.d/+short-name.<category>.md fragment. The release workflow replaces the name with the squash-merged pull
request number and credits the commit authors and co-authors, so do not write credits by hand. Release preparation runs
release-creator contributors to list first-time contributors. Use the skip news label for maintenance changes; bot
updates need a fragment only when the pull request supplies one.
Choose feature for added or removed Python support and new capabilities, change for changed behavior, bugfix for
fixes, and doc for user documentation. The other categories are breaking, security, performance, deprecation,
removal, and packaging. Keep each fragment about one user-visible change.
apply a consistent format to tox.ini files
installation
pip install tox-ini-fmt
as a pre-commit hook
See pre-commit for instructions
Sample .pre-commit-config.yaml:
- repo: https://github.com/tox-dev/tox-ini-fmt
rev: 1.10.0
hooks:
- id: tox-ini-fmt
args: [-p, 'fix_lint,type']
cli
Consult the help for the latest usage:
$ tox-ini-fmt --help
usage: tox-ini-fmt [-h] [-s | --check] [-p toxenv] tox_ini [tox_ini ...]
positional arguments:
tox_ini tox ini files to format
options:
-h, --help show this help message and exit
-s, --stdout print the formatted text to the stdout (instead of update in-place)
--check check files are formatted without writing them back (exit code 1 on change)
-p toxenv tox environments that pin to the start of the envlist (comma separated)
what does it do?
It does not
- Format any other section beside
tox/testenv:*(other than put this sections to the end of the file)
General
booleanfields are normalized totrueorfalse- all fields are stripped of white space on both end
- values that contain a list are split one value per line (PR/merge friendly)
- indent multi-line values by four spaces, and start on new line
- substitutions within multi-line (excluding
commands) are moved to the start of the list (order kept)
Ordering of sections
Applies the following section order:
toxtestenvtestenv:*-py/pypyenvs are ordered in decreasing order by python version, then apply the order defined withinenvlistpart oftoxsection, you can pin tox elements to the start by using the-pflag- any other section defined within the file
tox section
Order by:
envlist- multi-line, start withpyenvs in decreasing python order, then same withpypy, then everything elseisolated_build-booleanfieldskipsdist-booleanfieldskip_missing_interpreters-booleanfieldminversion
testenv section
Order by:
descriptionpassenv- multi-line, one environment name to pass per line, sorted by namesetenv- multi-line, one environment name-value to set per line in format ofkey=value, sorted by key+valuebasepythonskip_install-booleanfieldusedevelop-booleanfielddeps- multi-line, order by package name (but keep dependencies with package names separate at end), normalize format to remove extra spacesextras- multi-line, one extra env per lineparallel_show_output-booleanfieldcommands- one command per line, commands that wrap over multiple lines are indented with line two or later by extra four spaces
Metadata
Release files for tox-ini-fmt 1.10.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| tox_ini_fmt-1.10.1.tar.gz | 22.3 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| tox_ini_fmt-1.10.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 37.6 kB
Release files / tox_ini_fmt-1.10.1.tar.gz
| Download URL | tox_ini_fmt-1.10.1.tar.gz |
|---|---|
| Size | 22.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
873cecb8fbb11908ff0deab5a1ef0bab169bac5d138685840dec5e0bb7b51ace
|
|
BLAKE2b-256 checksum How to use checksums |
ff15fce615e2dea8adaa6eccb3cc7e9ae3587e8bf9bb2fb9948fc3c6c8ce8639
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 27, 2026.
Transparency logRelease files / tox_ini_fmt-1.10.1-py3-none-any.whl
| Download URL | tox_ini_fmt-1.10.1-py3-none-any.whl |
|---|---|
| Size | 15.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e68db293f20ec2d18f5e0f6129debbae415202c69a4707ffd45d71910f0fb832
|
|
BLAKE2b-256 checksum How to use checksums |
fbd4a8fe1fb050f0b525604b63670ac13ca1c04488abcaa7e58a035638bf761a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Oct 27, 2026.
Transparency logSecurity for tox-ini-fmt 1.10.1
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for tox_ini_fmt-1.10.1.tar.gz
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 Oct 27, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.