Issue
TOX_CONFIG_FILE is documented to be a way to specify a user-level configuration file, to set defaults to be used. There is a default for the configuration file as well, but the behavior differs when the file is automatically discovered vs. being explicitly specified.
In the examples below, the A and B outputs are correct, but the C output is not, even though TOX_CONFIG_FILE is set to point to the same file that is automatically used when it is not set.
Environment
Provide at least:
- OS: Debian Bookworm
- tox version: 4.3.5 installed using
pipx
Minimal example
$ mkdir foo
$ cd foo
$ cat > tox.ini << EOF
[tox]
[testenv:foo]
[testenv:bar]
[testenv:baz]
EOF
$ tox list (A)
default environments:
py -> [no description]
additional environments:
foo -> [no description]
bar -> [no description]
baz -> [no description]
$ mkdir $HOME/.config/tox
$ cat > $HOME/.config/tox/config.ini << EOF
[tox]
workdir=/tmp
EOF
$ tox list (B)
default environments:
py -> [no description]
additional environments:
foo -> [no description]
bar -> [no description]
baz -> [no description]
$ export TOX_CONFIG_FILE=$HOME/.config/tox/config.ini
$ tox list (C)
default environments:
py -> [no description]
Issue
TOX_CONFIG_FILE is documented to be a way to specify a user-level configuration file, to set defaults to be used. There is a default for the configuration file as well, but the behavior differs when the file is automatically discovered vs. being explicitly specified.
In the examples below, the
AandBoutputs are correct, but theCoutput is not, even though TOX_CONFIG_FILE is set to point to the same file that is automatically used when it is not set.Environment
Provide at least:
pipxMinimal example