#8734: make sage variables unique in maxima
-------------------------------------+-------------------------------------
Reporter: jason | Owner: jason
Type: defect | Status: needs_review
Priority: major | Milestone: sage-6.3
Component: interfaces | Resolution:
Keywords: | Merged in:
Authors: Jason Grout, Ralf | Reviewers: Volker Braun, Paul
Stephan | Zimmerman, Karl-Dieter Crisman
Report Upstream: N/A | Work issues:
Branch: | Commit:
u/rws/ticket/8734-1 | 793bb058a06b3dfb31c6029f6c30960d1dee8cc7
Dependencies: #15530 | Stopgaps:
-------------------------------------+-------------------------------------
Comment (by kcrisman):
> > So, in my opinion, unless someone comes up with a better solution,
this ticket will have to wait until Sage is Py-3.
>
> which may be a very long time.
Indeed.
> It nice to do things in a Py2/Py3 compatible way if possible (which can
be done here, I think), but if not we'll just have to fix it if/when sage
transitions from Py2 to Py3.
I'm not quite clear on why this is the case. I thought you said above to
not let the perfect be the enemy of the good ;-) It seems like just
raising the original exception is a good compromise here; at the very
least it should give ''some'' information, right?
--
Ticket URL: <http://trac.sagemath.org/ticket/8734#comment:50>
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.
