We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
If I have this:
[tool.tox] requires = ["tox>=4.21"] env_list = ["3.13", "3.12", "type", "doc"] ...
The old tox does not read it and ignores it.
If I change it like this:
[tool.tox] legacy_tox_ini = """ [tox] min_version = 4.21 """ env_list = ["3.13", "3.12", "type", "doc"] ...
The old tox reads it and updates tox in the provision venv. However, the TOML-native configuration is ignored by the new tox.
I believe this could be solved if the new tox preferred the TOML-native configuration over legacy_tox_ini if both exist.
I could stick with legacy_tox_ini unless I know all environments are fully updated to tox > 4.21.
Thanks
The text was updated successfully, but these errors were encountered:
PR welcome 👍 likely just need to swap it here. https://github.com/tox-dev/tox/blob/2bf065a/src/tox/config/source/discover.py#L22 and add test to confirm it 👍 plus updating the docs.
Sorry, something went wrong.
I think this is useful, so I'll try to dedicate some time to work on this this week, but no promises.
tox.toml
tox.ini
No branches or pull requests
What's the problem this feature will solve?
If I have this:
The old tox does not read it and ignores it.
If I change it like this:
The old tox reads it and updates tox in the provision venv.
However, the TOML-native configuration is ignored by the new tox.
Describe the solution you'd like
I believe this could be solved if the new tox preferred the TOML-native configuration over legacy_tox_ini if both exist.
Alternative Solutions
I could stick with legacy_tox_ini unless I know all environments are fully updated to tox > 4.21.
Thanks
The text was updated successfully, but these errors were encountered: