#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 nbruin):

 Replying to [comment:48 rws]:
 > Secondly, to ask interactively for a missing assumption a message has to
 be given in the terminal different from the error message tied to the
 original `RuntimeError`. So, simply re-raising is not an option if you do
 not like `RuntimeError: ECL says: Maxima asks: Is _SAGE_VAR_a an
 integer?`.

 In that case we know exactly what happened and the original traceback
 doesn't have to be kept. Raising a a fresh exception with a fresh
 traceback should be fine. It's when you find that the `RuntimeError`
 you've just caught is *not* the one you expected that the original
 traceback is valuable. And in that case you probably don't want to mess
 with the exception object itself either, so a bare `raise` should do the
 trick. The scenario of changing the error object but keeping the original
 traceback should be quite rare.

 > 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. 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.

--
Ticket URL: <http://trac.sagemath.org/ticket/8734#comment:49>
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.

Reply via email to