On 2014-11-21 18:21, Volker Braun wrote:
Its not brain surgery, but you want
1) Apply the preparser, possibly other input transformations
2) handle syntax errors from the preparser and show an appropriate error
(not: a traceback inside the preparser)
3) handle errors from the string -> ast compilation and show an
appropriate error
4) put the source into traceback.linecache
5) beautify the traceback
I assume with "beautify" you mean the graphical layout of the traceback?
Because IPython doesn't really change the contents of the traceback
(like unpreparsing).
IPython does all these things already.
I think you don't understand what #71 is about. What needs to be
implemented for #71 is mostly stuff which IPython *doesn't* do. Maybe
you think it *should* be in IPython, but I feel that's not what IPython
is about.
Loading code from a file is just loading + evaluating the loaded string.
It's *way* more than just that. It's also keeping track of the
unpreparsed and preparsed code for displaying tracebacks (currently in
Sage, code loaded with load() has no traceback at all). For attach(),
it's also checking whether the file has changed.
Jeroen.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
