Hi Marco and Conrado, On 20 Mai, 16:23, Conrado PLG <conrado...@gmail.com> wrote: > On Apr 19, 11:10 am, Marco Streng <marco.str...@gmail.com> wrote: > > > Hi sage-devel, > > > When debuggin code that is loaded into or attached to a Sage session, > > the tracebacks are not very informative: they refer to <string> instead > > of to the file name, and give no line numbers or code snippets. This > > makes it hard to find out where the error is. > > I was just going to post the same bug. It used to work, for example, > in Sage 4.3.
I am not sure what is used to create the tracebacks. But I could imagine that it uses stuff from sage.misc.sageinspect or sage.misc.edit_module. If this is the case, then it could help to use the patches from #9976 (merged in sage-4.7.1.alpha0) and #11298. Both patches greatly improve the functionality of introspection (e.g., you can inspect interactively defined Cython code). I will test whether they help with your tracebacks. And #11298 needs review, btw. Cheers, Simon -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
