#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 nbruin):
Replying to [comment:11 tmonteil]:
> So, this should not require much work to update, but perhaps there are
other ways to modify an environment variable in Python ?
You don't really need to fix those in-situ. You just need to trigger
saving the original value of the variables involved sage-env. I suspect
that will be much more robust than trying to track down every site where
the environment gets modified.
--
Ticket URL: <http://trac.sagemath.org/ticket/9386#comment:12>
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.
