#10286: sage-native-execute does not unset path etc.
-------------------------------------------------------------------------------------------+
Reporter: vbraun
| Owner: jason
Type: defect
| Status: needs_review
Priority: major
| Milestone: sage-5.3
Component: misc
| Resolution:
Keywords: sage-native-execute jmol LD_LIBRARY_PATH original save
restore sage-env | Work issues:
Report Upstream: N/A
| Reviewers: Leif Leonhardy
Authors: Volker Braun
| Merged in:
Dependencies:
| Stopgaps:
-------------------------------------------------------------------------------------------+
Comment (by nbruin):
Replying to [comment:6 jdemeyer]:
> Is this still relevant? Why is `sage-native-execute` needed anyway?
I think it still is. For instance if you start up magma (in the notebook
for instance), it's run via `sage-native-execute`. If you do anything in
the magma startup script that depends on having paths/environment properly
set, it won't work. For a while, it meant I couldn't use magma through the
notebook (see #9386). I worked around it by restoring the environment in
the magma startup script itself.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/10286#comment:7>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
