#5157: if the mwrank interface is interrupted from the notebook (!) it stays
broken for the rest of the sage session
----------------------+-----------------------------------------------------
Reporter: was | Owner: was
Type: defect | Status: new
Priority: critical | Milestone: sage-3.3
Component: algebra | Keywords:
----------------------+-----------------------------------------------------
This has been driving me nuts for a while. If you do
{{{
sage: EllipticCurve(997).gens(use_database=False)
[[press control-c]]
sage: EllipticCurve([1,3]).gens(use_database=False)
Traceback (most recent call last):
...
RuntimeError: [Errno 9] Bad file descriptor
Error evaluating [0, 0, 0, 1, 3] in Mwrank
}}}
This is from the notebook. The same sequence works correctly from the
command line (no bad file descriptor).
I think the problem is that the notebook sends multiple control-c's and
ends up killing sage properly restarting mwrank. On the command line one
has:
{{{
sage: EllipticCurve(997).gens(use_database=False)
...
KeyboardInterrupt: Restarting Mwrank (WARNING: all variables defined in
previous session are now invalid)
sage: EllipticCurve([1,3]).gens(use_database=False)
[(-1 : 1 : 1)]
}}}
BUT, if you hit control-c twice in rapid succession, then mwrank gets
broken even on the command line (I just verified this).
The fix is to make it so the mwrank interface recovers automatically if it
gets left in this state.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/5157>
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
-~----------~----~----~----~------~----~------~--~---
