#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):
Ah good. Looks like we came up with about the same solution relatively
independently. Some things:
- it's nice if we can export variables and preserve their unset status.
Then you can just do `sage_export UNSET_VARIABLE` and clobber it later (I
did that by letting `sage_export` differentiate between 1 and 2
parameters)
- you don't have to rely on a magic value to store whether or not a
variable is unset: you can just unset the backup variable
- bash does have local variables for functions.
- you can avoid using grep.
--
Ticket URL: <http://trac.sagemath.org/ticket/9386#comment:14>
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.
