-
-
Notifications
You must be signed in to change notification settings - Fork 528
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TOX_CONFIG_FILE overrides local config #2890
Comments
Note: 'work_dir' is misspelled in the user-level config file in the example but the behavior does not change if it is spelled correctly. |
confirmed, reproducible on tox 4.3.5 |
The workaround here is to specify
I believe the crux of the problem is that tox is overloading the name tox/src/tox/config/cli/parser.py Line 328 in 7753e72
☝️ here Line 28 in 7753e72
☝️ here still unteasing the true root cause. |
There's a fundamental incompatibility here, where tox implicitly looks for tox/src/tox/config/cli/env_var.py Line 23 in 7753e72
I propose that we rename the user config envvar to
With this change, passing So the fix here could be as simple as renaming this conflicting variable and updating the configuration. Should I proceed @gaborbernat? |
Allow overriding the user config file without overriding the main config file. Fix tox-dev#2890
Yeah please. |
@masenf Thank you for tracking this down. The root cause seems so obvious in hindsight :-) |
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
andB
outputs are correct, but theC
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:
pipx
Minimal example
The text was updated successfully, but these errors were encountered: