-
-
Notifications
You must be signed in to change notification settings - Fork 531
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
{env:} macro is not expanded in setenv if the default value contains {envdir} #301
Comments
I just tried the example in tox 2.4.1 and the problem still persists. |
I got bit by this as well. From my limited understanding of the code, it looks like I may take another stab at this at a later date, but for now, wanted to post the test function I worked up which exercises a few related cases:
|
Hey @eli-collins thanks for sharing that. Mind to turn that into a PR that can serve as a reproducer that we'll XFAIL until we have it fixed? |
In case of a nested substitution values are expanded starting from the innermost expression and continued until no successful substitutions could be found.
In case of a nested substitution values are expanded starting from the innermost expression and continued until no successful substitutions could be found.
config: expand nested substitutions (fixes #301)
The following tox target will not expand {env:} macro with the default value (the substitution for {envdir}):
Once I replace {envdir} with a hardcoded value, it expands {env:} correctly using the default value.
The text was updated successfully, but these errors were encountered: