Re: [matplotlib-devel] "ValueError: too many values to unpack" building docs

2009-09-22 Thread Michael Droettboom
It's also an overridable parameter in conf.py. Of course, it works with the conf.py in SVN, but do you perhaps have any local changes to it? Mike Sandro Tosi wrote: > Hi all, > I'm a bit unsure if this is really a problem in the code or it's my > machine that has problem (I didn't manage to tes

Re: [matplotlib-devel] "ValueError: too many values to unpack" building docs

2009-09-22 Thread Michael Droettboom
On second look, I think it's the "--small" commandline option that breaks this. I hadn't tested my recent changes to the plot directive with that flag. The new version of make.py in SVN r7815 should fix this. Mike Sandro Tosi wrote: > Hi all, > I'm a bit unsure if this is really a problem in

[matplotlib-devel] Comparing pdf output in tests

2009-09-22 Thread Jouni K . Seppänen
I am thinking about adding pdf comparison ability to compare_images. One simple way to do this would be to convert pdf files to pngs using Ghostscript: if we store reference pdf files, and both the reference file and the result of the test are converted using with exactly the same version of gs, th

Re: [matplotlib-devel] Comparing pdf output in tests

2009-09-22 Thread Michael Droettboom
Jouni K. Seppänen wrote: > I am thinking about adding pdf comparison ability to compare_images. One > simple way to do this would be to convert pdf files to pngs using > Ghostscript: if we store reference pdf files, and both the reference > file and the result of the test are converted using with e

Re: [matplotlib-devel] Comparing pdf output in tests

2009-09-22 Thread Andrew Straw
Michael Droettboom wrote: > Jouni K. Seppänen wrote: > >> I am thinking about adding pdf comparison ability to compare_images. One >> simple way to do this would be to convert pdf files to pngs using >> Ghostscript: if we store reference pdf files, and both the reference >> file and the result o

[matplotlib-devel] 0.99.1 and the setup.cfg file

2009-09-22 Thread jason-sage
I just downloaded 0.99.1 and ran into some problems using it in Sage. Basically, in the tar.gz file, there was a setup.cfg file, which had the following: Note that some options are already uncommented, forcing a build of tkagg, wxagg, and macosx backends, and forcing the default backend to be

Re: [matplotlib-devel] 0.99.1 and the setup.cfg file

2009-09-22 Thread John Hunter
On Tue, Sep 22, 2009 at 5:38 PM, wrote: > I just downloaded 0.99.1 and ran into some problems using it in Sage. > Basically, in the tar.gz file, there was a setup.cfg file, which had the > following: This was a bug in the tarball -- mpl doesn't keep a copy of setup.cfg in svn and shouldn't ship

Re: [matplotlib-devel] Comparing pdf output in tests

2009-09-22 Thread Jouni K . Seppänen
Andrew Straw writes: > Michael Droettboom wrote: >> We can probably standardize the version of gs on the buildbot machines, >> but it's been very useful up to now to have tests that can run on a >> variety of developer machines as well. >> > I understood Jouni's idea to be to save the .pdfs as

Re: [matplotlib-devel] Comparing pdf output in tests

2009-09-22 Thread Andrew Straw
Jouni K. Seppänen wrote: > Andrew Straw writes: > > >> Michael Droettboom wrote: >> >>> We can probably standardize the version of gs on the buildbot machines, >>> but it's been very useful up to now to have tests that can run on a >>> variety of developer machines as well. >>> >>>