#9386: sage-native-execute leaves traces of sage
-------------------------------------+-------------------------------------
Reporter: nbruin | Owner: tbd
Type: defect | Status: needs_review
Priority: major | Milestone: sage-6.4
Component: packages: | Resolution:
standard | Merged in:
Keywords: | Reviewers:
Authors: Thierry Monteil | Work issues:
Report Upstream: N/A | Commit:
Branch: | 920c897ec3c439d772f7dfef1a420fb9aec0baea
u/tmonteil/sage_native_execute_leaves_traces_of_sage| Stopgaps:
Dependencies: |
-------------------------------------+-------------------------------------
Comment (by tmonteil):
I agree that once Sage exports a variable, we lose the information on
whether it existed before (apart from `LD_LIBRARY_PATH` and `PATH` which
have a hand-made specific workaround). This is already a problem with the
`..._proxy` variables, or even `LC_ALL`. Instead of storing the whole
environment on a central place, i was thinking of having a modified
`export` function that applies to all Sage, that stores the previous value
if it is not already stored (with a special flag to remember that the
variable did no exist, which seems slightly different than being the empty
string). So somehow, each export costs two exports, but it remains a local
operation that passes the required info along subprocesses, so it is
probably easier to maintain. Then, it suffices to copy-or-unset those
values when `sage-native-execute` is called. I don't know which is best.
--
Ticket URL: <http://trac.sagemath.org/ticket/9386#comment:9>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.
