On Wed, May 20, 2009 at 3:37 PM, John Hunter wrote:
> On Wed, May 20, 2009 at 3:30 PM, James Evans
> wrote:
> > When I wrote the test stuff I had forgotten all about the matplotlibrc
> stuff. I think it would make sense to just use a default
> > (empty) matplotlibrc for the tests, this way we a
On Wed, May 20, 2009 at 3:30 PM, James Evans wrote:
> When I wrote the test stuff I had forgotten all about the matplotlibrc stuff.
> I think it would make sense to just use a default
> (empty) matplotlibrc for the tests, this way we are always testing against
> the defaults. If the defaults e
changes to note if there is any negative
consequences of the change.
Do the defaults ever differ based upon platform? Backend? Phase of the moon?
--James Evans
> Date: Wed, 20 May 2009 10:32:12 -0500
> From: John Hunter
> Subject: Re: [matplotlib-devel] Tests and matplotlibrc
>
On Wed, May 20, 2009 at 10:27 AM, Ryan May wrote:
> Thanks, I wasn't aware of that. It seems that if I just put an empty
> matplotlibrc file in that directory, it serves the same purpose. Can I just
> check that in (perhaps containing only a clarifying comment) so that it
> stays in sync with t
On Wed, May 20, 2009 at 10:20 AM, John Hunter wrote:
> On Wed, May 20, 2009 at 10:12 AM, Ryan May wrote:
> > Hi,
> >
> > Is there any way to make the tests force a certain default set of
> rcparams?
> > When I first ran the test suite just now, I got a lot of image comparison
> > failures becaus
On Wed, May 20, 2009 at 10:12 AM, Ryan May wrote:
> Hi,
>
> Is there any way to make the tests force a certain default set of rcparams?
> When I first ran the test suite just now, I got a lot of image comparison
> failures because I have my default font set to 10 in my matplotlibrc.
> Changing thi
