#9386: sage-native-execute leaves traces of sage
-------------------------------------+-------------------------------------
Reporter: nbruin | Owner: tbd
Type: defect | Status: needs_work
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:15 jdemeyer]:
> ''Unsetting'' `PATH`? Then nothing will work...
Would you care to elaborate? If I do
{{{
$ . sage_restore.sh
$ sage_export PATH
$ PATH=bad_stuff:$PATH
$ sage_restore
}}}
I end up with my original path back, not with an unset path.
I fully expect that the script needs further tuning and probably lots of
quotes in all kinds of places to catch all kinds of little quirks (it's
scary to think that shell scripts are the weapon of choice for complicated
configuration tasks), but I think the general mechanism is fine. Do you
have better suggestions? I'm not married to my implementation. If you come
up with something better I'm sure we'll be happy to adopt that.
However, if you're going to suggest to unset PATH then I don't think we'll
be so eager, because indeed, I think if you do that, you'll break a lot.
--
Ticket URL: <http://trac.sagemath.org/ticket/9386#comment:16>
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.
