William Stein wrote: > >> def f(x): > >> blah > >> > >> It's really easy to know where the definition ends. > > > > Parsers have this funny way of bit-rotting over time... I'll write > > tests :) > > Definitely! > > > BTW, inspect.py does not parse source code. All the information is > > stored at compile time (as you would expect -- the syntax tree is still > > live) and inspect.py just provides a nicer interface to query the > > stored information. > > You could modify sagex to save the parse information at compile time. > It parses .pyx files, then discards the results after using them > to generate .c files.
I could, but if I'm not going to embed the results in docstrings I'd have to find them at run-time, and the hassles of doing that are probably worse than the hassles of parsing in the first place. On an unrelated note: how do I alter what ipython does for ? and ?? (this might be a question for Fernando Perez). We have code in server.support that duplicates what ipython does; we should factor that out and modify ipython to run our unified, sagex enhanced, version. Nick --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~----------~----~----~----~------~----~------~--~---
