-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Interaction of setenv and cmd interpolation #24353
Labels
minor change
Marginal behavior change acceptable for a minor release
Comments
Just ran into this again. We missed 1.0 of course, but marking for triage on what to do here. |
Quick discussion with @JeffBezanson, one possible solution may be to allow interpolation in first position, but make it an error everywhere else. |
Also, by |
Triage decision:
|
StefanKarpinski
added
minor change
Marginal behavior change acceptable for a minor release
and removed
triage
This should be discussed on a triage call
labels
Sep 13, 2018
Keno
added a commit
that referenced
this issue
Apr 18, 2019
Too late for 1.2 for which this was originally marked, but nevertheless, it's a quick change, so might as well get it in now and have it be available in 1.3. Fixes #25353
Keno
added a commit
that referenced
this issue
Apr 18, 2019
Too late for 1.2 for which this was originally marked, but nevertheless, it's a quick change, so might as well get it in now and have it be available in 1.3. Fixes #25353
Keno
added a commit
that referenced
this issue
Apr 18, 2019
Too late for 1.2 for which this was originally marked, but nevertheless, it's a quick change, so might as well get it in now and have it be available in 1.3. Fixes #24353
Keno
added a commit
that referenced
this issue
Apr 22, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I think interpolating a cmd that had its env set should either raise an error or propagate the environment. Current behavior:
The text was updated successfully, but these errors were encountered: