#7509: notebook -- make it possible to debug Python code in the notebook, e.g.,
something like pdb that works in the notebook
---------------------------+------------------------------------------------
Reporter: was | Owner: boothby
Type: enhancement | Status: needs_work
Priority: major | Milestone: sage-5.0
Component: notebook | Keywords:
Work_issues: | Upstream: N/A
Reviewer: David Roe | Author:
Merged: | Dependencies:
---------------------------+------------------------------------------------
Comment(by was):
Replying to [comment:17 roed]:
> This is while debugging the example
> {{{
> EllipticCurve([0,0])
> }}}
>
> If you type in a command (e.g. "print ainvs"), execute it, switch to a
different frame and press enter again, nothing happens: it doesn't execute
the print statement in the new frame. You can get it to execute by
hitting the button though. If you type in a different command, then it
starts executing upon pressing enter again.
>
This is a fundamental limitation of @interact right now. I can make a
remark about this in the docstring.
I'll fix + improve the doctests and post a new patch.
> There are doctest failures in listing, since you updated the functions.
>
> Another small request would be to add a doctest to the evaluate function
that demonstrates the case that a user types in a command to the text box
which raises an error.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/7509#comment:18>
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 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.
