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 ever change it would also
allow us to more easily catch those 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?
Date: Wed, 20 May 2009 10:32:12 -0500
From: John Hunter <jdh2358@…149…>
Subject: Re: [matplotlib-devel] Tests and matplotlibrc
To: Ryan May <rmay31@…149…>
Cc: Ted Drain <ted.drain@…179…>, "Evans, James R"
<james.r.evans@…179…>, Matplotlib Devel???
Content-Type: text/plain; charset=ISO-8859-1
On Wed, May 20, 2009 at 10:27 AM, Ryan May <rmay31@...149...> 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 the current matplotlib defaults?
Not sure what is the best way here -- one is to put in an rc w/
everything uncommented for the tests, so that even if the mpl defaults
change the regression suite won't break. The other is to assume the
defaults in the test suite (empty rc) and if someone changes an rc
default it breaks the test suite. Perhaps James or Ted have a