#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: positive_review
Priority: major | Milestone: sage-5.0
Component: notebook | Keywords:
Work_issues: | Upstream: N/A
Reviewer: David Roe | Author:
Merged: | Dependencies:
---------------------------+------------------------------------------------
Comment(by whuss):
Replying to [comment:14 was]:
> Hi whuss. Thanks. I'm reluctant to do syntax hilighting that way
(the way you do in your patch, just on code), since it is very often
completely wrong if we don't hilight the whole file. We need to hilight
the whole file, then grab just the relevant part back.
I want to avoid highlighting the whole file, since this can be quite slow.
On my computer it takes about 2 seconds to load and highlight
graphs/generic_graph.py.
I think the main problem when one gets wrong highlighting is when the code
fragment
starts in the middle of a docstring. At ticket:12451 there is an improved
patch which
detects when the code fragments starts in the middle of a tripple quoted
string, and does the correct highlighting in this case.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/7509#comment:22>
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.
