On 26.03.2012, at 7:43PM, John Hunter wrote:
> On Mon, Mar 26, 2012 at 12:00 PM, Russell Owen <[email protected]> wrote:
> On Mar 24, 2012, at 12:16 PM, Sandro Tosi wrote:
>
> > On Sat, Mar 24, 2012 at 18:13, Derek Homeier
> > <[email protected]> wrote:
> >> I used the 1.1.0 version to build with the fink Python installation on
> >> MaxOS X
> >> and everything seems to work there, passing the tests at least (does
> >> pylab.test('full')
> >> execute all tests? It seems a rather small number…).
> >
> > to run tests I use:
> >
> > python -c "import matplotlib as m ; m.test(verbosity=1)"
>
> Thank you for the test instructions. That's a much more complete test than I
> had been using. I get the following one failure on Mac OS X 10.6 using my new
> binary installer (results are appended). I'm also concerned about the
> complaint:
> """
> /Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/site-packages/matplotlib/__init__.py:921:
> UserWarning: This call to matplotlib.use() has no effect
> because the the backend has already been chosen;
> matplotlib.use() must be called *before* pylab, matplotlib.pyplot,
> or matplotlib.backends is imported for the first time.
> """
> which suggests a test that is mis-written.
>
> At the end of the tests we try and switch back to the users original backend
> (we switch into agg at the start) in case the user is running interactively.
> This warning is mostly harmless, and doesn't indicate a problem with any
> tests. It appears you have just the one failure on fonts-styles.
>
I also had two failures of this type on my first attempt to test the package;
now when
testing within the fink build environment, everything passes. This might have
to do
with the fontconfig setup, not sure if I can reproduce it any more or nail it
further down.
> Ran 1061 tests in 344.859s
>
> FAILED (KNOWNFAIL=541, failures=1)
Russel, you may also want to check the testing dependencies mentioned in
connection
with the tests under Windows in this thread - installing inkscape in addition
to ghostscript
and pil got me rid of the Known Failures (due to missing functionality for
comparing PDF
and SVG output) as well.
Does anyone see a problem with running the tests with 'python -B'? Otherwise
I'd need to
get rid of the byte-compiled files in the build directory afterwards, as they
would cause the
package validation to fail.
Cheers,
Derek
------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
