On Tue, Sep 8, 2009 at 10:46 AM, Andrew Straw<straw...@astraw.com> wrote:
> While the default test usage should probably set as much as possible to > ensure things are identical, we also want to be able to test other code > paths, so I think I'll add some kind of kwarg to matplotlib.test() to handle > non-testing-default rcParams. I think setting lots of things, including the > font, explicitly in the default case is a good idea. > > Question for the rcParams experts: Can we save a copy of it so that we can > restore its state after matplotlib.test() is done? (It's just a dictionary, > right?) I committed this change > Yes, I completely agree. In the matplotlib.testing.image_comparison() > decorator, we right now have only a single image comparison algorithm based > on RMS error. Perhaps we could try the perceptual difference code you linked > to? Also, maybe we could simply turn font rendering off completely for a > majority of the tests? Or maybe the tests should be run with and without > text drawn, with much lower error tolerances when there's no text? Perhaps with hinting turned off this won't be necessary. Ie, maybe we can get more agreement across a wide range of freetype versions w/o hinting. Are you planning on committing the unhinted baselines? JDH ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
