Jeroen Demeyer wrote: > Hello, > > I have often been annoyed by the lack of tracebacks given in warning > messages. Something, I have even replaced a warning with an exception, > just such that I could get a useful traceback. > > Using the warnings and traceback modules, it is possible to display a > traceback with a warning message. This will of course make the output of > warnings a lot more verbose. The warning messages might also be more > easily confused with error messages. So I'm not convinced that we should > do this by default.
PLEASE DON'T DO THIS BY DEFAULT. It's already annoying that here and there instead of proper error messages (only!) useless lengthy tracebacks flood the terminal, even in "typical error situations" (not to mention automatically starting GDB by default in some cases where it /might/ be appropriate to /some/). -leif > But we could certainly do this in the doctester (see #21191 for that). > This would already be quite useful, the disadvantages do not really seem > to apply in that case. The only issue is that warnings would look > different in interactive usage and in doctests. But this is already the > case for exception messages (IPython formats them in a different way). > > What do you think? -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
