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
sage.env._add_variable_or_fallback: Get rid of $variable substitution feature #23762
Comments
comment:1
I think the variable substitution scheme was introduced in #13432. I've asked there about its rationale: I don't want to remove this without trying to understand why it was introduced in the first place. In the mean time, I have a branch which makes the change from strings to variables: |
Branch: u/jhpalmieri/env |
Dependencies: #23758 |
Commit: |
comment:4
This branch passes doctests for me, but I want to wait to set it to "needs_review" for some feedback from the participants at #13432. |
comment:5
Potential conflict with #21535. |
comment:7
I don't think I ever saw the original version of this, but it would be superseded now by #27040 (which accomplishes the same goal). |
As discussed in #23758, the feature of
_add_variable_or_fallback
to do variable substitution seems unnecessarily complex.All uses later in that module such as
can be replaced by simple use of Python variables (which all exist in the
sage.env
module)This also will have a clearer failure mode -- instead of leaving an unsubstituted $SAGE_LOCAL in a string if that variable is not set for some reason, an error will be raised.
Depends on #23758
Depends on #21535
CC: @jhpalmieri
Component: build
Branch/Commit: u/jhpalmieri/env @
c7cff80
Issue created by migration from https://trac.sagemath.org/ticket/23762
The text was updated successfully, but these errors were encountered: