Jouni K. Seppänen wrote: > The matplotlib.use() function was always a no-op after importing pylab, > and there were occasional questions about it on the mailing list. It was > changed fairly recently to raise an error in this case. Bug #1855454 > points out that this is not backward compatible: an application that > calls use() too late didn't do anything before the change, but now gets > stopped with a traceback. I suggest changing the error to a warning, > which I think would still deliver the message but would be compatible > with (broken) legacy code. What do you think? > > http://sourceforge.net/tracker/index.php?func=detail&aid=1855454&group_id=80706&atid=560720 >
Good point. I probably went overboard when making the original change in October, so I have now changed it to a warning as you suggest. Eric ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
