[matplotlib-devel] Change matplotlib.use error to a warning?
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 -- Jouni - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] Problem with Agg Ellipses
On Dec 25, 2007 5:39 AM, Mark Bakker <[EMAIL PROTECTED]> wrote: > Tedd, Michael - > > Sorry to join this discussion late, but wouldn't it be easier to use a > representation of an ellipse in complex variables? That's what I have been > using and it seems pretty quick to me. The main point we are discussion is not how to represent the ellipse, but what geometric primitives to use to render the ellipse. Earlier versions of mpl used a polygon, then we added support for a 4 spline approximation to reduce the error of the approximation. This too did not have sufficient accuracy, and so Michael added an 8 spline approximation (Ellipse) as well as an adaptive approximation (Arc). JDH - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] Change matplotlib.use error to a warning?
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/vse012070mrt/direct/01/ ___ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
[matplotlib-devel] grammar nanny
On the what's new page, http://matplotlib.sourceforge.net/whats_new.html it says "expand it's coverage" but it should be "expand its coverage". Happy holidays. Dr. Tom -- My brother, when you have a virtue, and it is your own virtue, you have it in common with no one. Thus spoke Zarathustra. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
