#5442: preparser or magma.eval bug?
----------------------------+-----------------------------------------------
Reporter: kohel | Owner: was
Type: defect | Status: closed
Priority: minor | Milestone:
Component: user interface | Resolution: invalid
Keywords: |
----------------------------+-----------------------------------------------
Changes (by was):
* status: new => closed
* resolution: => invalid
Comment:
> The problem is that either preparse_ipython or magma.eval is too
> naive, inserting a ';' rather than waiting for the completion
> of the expression.
For the record, this was on purpose and is by design. The magma
interpreter via magma.eval is a blocking call, and if you send it
a chunk of code without a semicolon it will block forever. If one
were to do what you suggest above, then typing
magma.eval('2+2')
would lead to a total hang of Sage.
I'm marking this ticket as invalid unless you see a good reason to totally
change the design of the interface to be nonblocking, which I doubt you'll
do unless you really understand how they work and what the many negatives
of doing that are.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/5442#comment:1>
Sage <http://sagemath.org/>
Sage - Open Source Mathematical Software: Building the Car Instead of
Reinventing the Wheel
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
