On Tuesday, June 9, 2015 at 1:19:53 PM UTC+2, kcrisman wrote: > > I don't think so, the normal Python way is to show you a backtrace so you >>> can fix your mistake and not make up random default return values. >>> >> > If there is an error, but that's not what (apparently) happened here, only > a warning. In which event it should raise an Error of some kind, but it > didn't (did it?) and not return anything. >
A normal backtrace is also something that is generated as a special kind of output, and customized by IPython. The problem is that construction of the plot did not raise an error, even though it should have. Whenever you have an invalid object that fails while it prints itself you can't get the usual backtrace since you fail in the displayhook, and not while executing the command. This is why its such a bad idea to allow creation of bogous objects that then later fail over their feet when printing. > > >> The problem here is of course that the color function fc must be a >> function of two arguments instead of one. >> >> > Ah, that's what happens when I try to check something when I'm too tired > to read documentation - esp. of a ticket I was involved with (par. plot > coloring), worse luck. Good call. > > >> I can reproduce the crash, presumably you opened a bug for that? >> > > No, I couldn't get it to happen again - please do open a ticket if you > were able to reproduce it. Actually, I'd appreciate you opening and cc:ing > me and Niles on a ticket about the color function checking as well (in a > few minutes I'll be off the train in a no-internet zone for the day). > Thank you! > -- You received this message because you are subscribed to the Google Groups "sage-support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sage-support. For more options, visit https://groups.google.com/d/optout.
