-
-
Notifications
You must be signed in to change notification settings - Fork 529
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
Curly braces cannot be escaped in setenv definition since 3.20.0 #1690
Labels
bug:normal
affects many people or has quite an impact
Comments
Tagging @mkenigs as potential follow-up issue 👍 |
I've got a patch to fix this and the original problem (assuming I've understood it correctly), however I am also encountering a separate problem with |
jayvdb
added a commit
to jayvdb/tox
that referenced
this issue
Oct 17, 2020
This partially reverts commit 3c38762. Fixes tox-dev#1690
jayvdb
added a commit
to jayvdb/tox
that referenced
this issue
Oct 17, 2020
This partially reverts commit 3c38762. Fixes tox-dev#1690
Some basic misplaced |
jayvdb
added a commit
to jayvdb/tox
that referenced
this issue
Oct 18, 2020
This partially reverts commit 3c38762. Fixes tox-dev#1690
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Somewhat similar to #1502 , but this is a regression caused by #1656 , which has a test which is precisely what is not wanted. It appears there wasnt an issue created about that problem, but it appears to be that the runtime environment for the invoked commands contains backslashes. That should have been solved by leaving the tox substitution framework working as-is, and post-processing the substitutions when they are injected into the new process environment, to whatever extent that is possible (seems feasible to me, but maybe I have missed something).
The following emits
\{a\}
Removing the
\\
results in an startup error.The text was updated successfully, but these errors were encountered: