[sage-devel] Re: upgrading matplotlib and ignoring sage's matplotlibrc

2009-02-05 Thread Jason Grout
William Stein wrote: >> I'm just going to make a call on this, so that the new matplotlib gets into >> Sage ASAP.Jason's original proposal is: >> >> "So here's a proposal: Should Sage stop distributing a custom >> matplotlibrc, and ignore matplotlibrc files that already exist in the >> $DOT_S

[sage-devel] Re: upgrading matplotlib and ignoring sage's matplotlibrc

2009-02-05 Thread William Stein
On Thu, Feb 5, 2009 at 2:28 PM, William Stein wrote: > On Fri, Jan 30, 2009 at 10:52 AM, Jason Grout > wrote: >> >> Jason Grout wrote: >>> >>> Well, there is something to be said for what you said. We ship our own >>> version of matplotlib, which mostly likely is different than the system >>>

[sage-devel] Re: upgrading matplotlib and ignoring sage's matplotlibrc

2009-02-05 Thread William Stein
On Fri, Jan 30, 2009 at 10:52 AM, Jason Grout wrote: > > Jason Grout wrote: >> >> Well, there is something to be said for what you said. We ship our own >> version of matplotlib, which mostly likely is different than the system >> install. That means that their perfectly good default matplotli

[sage-devel] Re: upgrading matplotlib and ignoring sage's matplotlibrc

2009-01-30 Thread Nils Bruin
On Jan 30, 10:46 am, Jason Grout wrote: > Add a warnings handler which traps the Matplotlib deprecation > warning. This handler will compare the matplotlibrc with the one that > was distributed in the last release (maybe by checking a hash value). > If it is identical (i.e., the user hasn't mod

[sage-devel] Re: upgrading matplotlib and ignoring sage's matplotlibrc

2009-01-30 Thread Jason Grout
Jason Grout wrote: > > Well, there is something to be said for what you said. We ship our own > version of matplotlib, which mostly likely is different than the system > install. That means that their perfectly good default matplotlibrc file > might cause deprecation warnings for us. For t

[sage-devel] Re: upgrading matplotlib and ignoring sage's matplotlibrc

2009-01-30 Thread Jason Grout
William Stein wrote: > On Fri, Jan 30, 2009 at 8:52 AM, Carl Witty wrote: >> On Thu, Jan 29, 2009 at 5:49 PM, William Stein wrote: >>> On Wed, Jan 28, 2009 at 10:07 PM, Jason Grout >>> wrote: I just finished upgrading the matplotlib spkg to the newest version. See http://trac.sagemath

[sage-devel] Re: upgrading matplotlib and ignoring sage's matplotlibrc

2009-01-30 Thread William Stein
On Fri, Jan 30, 2009 at 8:52 AM, Carl Witty wrote: > > On Thu, Jan 29, 2009 at 5:49 PM, William Stein wrote: >> >> On Wed, Jan 28, 2009 at 10:07 PM, Jason Grout >> wrote: >>> >>> I just finished upgrading the matplotlib spkg to the newest version. >>> See http://trac.sagemath.org/sage_trac/tick

[sage-devel] Re: upgrading matplotlib and ignoring sage's matplotlibrc

2009-01-30 Thread Carl Witty
On Thu, Jan 29, 2009 at 5:49 PM, William Stein wrote: > > On Wed, Jan 28, 2009 at 10:07 PM, Jason Grout > wrote: >> >> I just finished upgrading the matplotlib spkg to the newest version. >> See http://trac.sagemath.org/sage_trac/ticket/4774 >> >> This version of matplotlib deprecates some of th

[sage-devel] Re: upgrading matplotlib and ignoring sage's matplotlibrc

2009-01-30 Thread Jason Grout
John Hunter wrote: > On Fri, Jan 30, 2009 at 9:30 AM, Ondrej Certik wrote: > >>> I *wish* matplotlib would replace their stupid deprecation warnings by >>> something that just updates the matplotlibrc file, and say makes a >>> copy of the old one. Is there any way we could catch the warnings an

[sage-devel] Re: upgrading matplotlib and ignoring sage's matplotlibrc

2009-01-30 Thread William Stein
On Fri, Jan 30, 2009 at 7:30 AM, Ondrej Certik wrote: > On Thu, Jan 29, 2009 at 5:49 PM, William Stein wrote: >> I *wish* matplotlib would replace their stupid deprecation warnings by >> something that just updates the matplotlibrc file, and say makes a >> copy of the old one. Is there any way

[sage-devel] Re: upgrading matplotlib and ignoring sage's matplotlibrc

2009-01-30 Thread Jason Grout
William Stein wrote: > On Wed, Jan 28, 2009 at 10:07 PM, Jason Grout > wrote: >> I just finished upgrading the matplotlib spkg to the newest version. >> See http://trac.sagemath.org/sage_trac/ticket/4774 >> >> This version of matplotlib deprecates some of the constructs found in >> Sage's matplot

[sage-devel] Re: upgrading matplotlib and ignoring sage's matplotlibrc

2009-01-30 Thread Ondrej Certik
On Thu, Jan 29, 2009 at 5:49 PM, William Stein wrote: > > On Wed, Jan 28, 2009 at 10:07 PM, Jason Grout > wrote: >> >> I just finished upgrading the matplotlib spkg to the newest version. >> See http://trac.sagemath.org/sage_trac/ticket/4774 >> >> This version of matplotlib deprecates some of th

[sage-devel] Re: upgrading matplotlib and ignoring sage's matplotlibrc

2009-01-29 Thread William Stein
On Wed, Jan 28, 2009 at 10:07 PM, Jason Grout wrote: > > I just finished upgrading the matplotlib spkg to the newest version. > See http://trac.sagemath.org/sage_trac/ticket/4774 > > This version of matplotlib deprecates some of the constructs found in > Sage's matplotlibrc (which is located in $

[sage-devel] Re: upgrading matplotlib and ignoring sage's matplotlibrc

2009-01-28 Thread Nick Alexander
> So here's a proposal: Should Sage stop distributing a custom > matplotlibrc, and ignore matplotlibrc files that already exist in the > $DOT_SAGE directories? I am +0, since I don't plot, but one could distribute a custom matplotlibrc saying that it is no longer used and pointing to likely l