-
-
Notifications
You must be signed in to change notification settings - Fork 511
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
Multi-line setup.cfg configs break command expansion #2847
Comments
This is expected; we could document it as a breaking change, but that's about it. |
Why do we support line separation for e.g. I just tried to use a comma as a separator... that won't work either.
It looks like use space as a separator works for both tox 3 and tox 4.
|
Yes, putting everything on one space-separated line is compatible with both cases. |
Think about the type of configuration. |
Issue
Since switching to version 4 (
4.2.6
specifically) from version 3, tox is treating multi-line entries insetup.cfg
differently, as they seem to be expanded over mulitple lines when the var is used in a command (see example below).Environment
pip list
of the host Python wheretox
is installed:Output of running tox
Provide the output of
tox -rvv
:For comparison, this is the output with the
tox
version in Ubuntu 22.10:Minimal example
The following
setup.cfg
reproduces the issue:Changing the definition as follows works with version 4, but is not backwards compatible:
The text was updated successfully, but these errors were encountered: