Re: [matplotlib-devel] "ValueError: too many values to unpack" building docs
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 test it in a clean > chroot). > > When building the doc (after having built mpl with python setup.py > build) I got the attached traceback. > > The strange fact is that 'formats' is indeed defined as a 2D list (At > the bottom of plot_directive.py). > > Thanks for considering, > > > > -- > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9-12, 2009. Register now! > http://p.sf.net/sfu/devconf > > > ___ > Matplotlib-devel mailing list > Matplotlib-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel -- Michael Droettboom Science Software Branch Operations and Engineering Division Space Telescope Science Institute Operated by AURA for NASA -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf ___ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] "ValueError: too many values to unpack" building docs
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 the code or it's my > machine that has problem (I didn't manage to test it in a clean > chroot). > > When building the doc (after having built mpl with python setup.py > build) I got the attached traceback. > > The strange fact is that 'formats' is indeed defined as a 2D list (At > the bottom of plot_directive.py). > > Thanks for considering, > > > > -- > Come build with us! The BlackBerry® Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart your > developing skills, take BlackBerry mobile applications to market and stay > ahead of the curve. Join us from November 9-12, 2009. Register now! > http://p.sf.net/sfu/devconf > > > ___ > Matplotlib-devel mailing list > Matplotlib-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel -- Michael Droettboom Science Software Branch Operations and Engineering Division Space Telescope Science Institute Operated by AURA for NASA -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf ___ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
[matplotlib-devel] Comparing pdf output in tests
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, there should be no font-rendering or antialiasing mismatches. Can we assume that all test computers will have some version of Ghostscript installed and callable as "gs"? -- Jouni K. Seppänen http://www.iki.fi/jks -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf ___ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] Comparing pdf output in tests
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 exactly the > same version of gs, there should be no font-rendering or antialiasing > mismatches. > > Can we assume that all test computers will have some version of > Ghostscript installed and callable as "gs"? > 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 don't know how different the output will be from different versions of gs -- maybe we should just try it and see. I have a pretty old version of gs on my RHEL4 box (7.07). If you want me to send you a png of a particular pdf to directly compare with yours before you even start with the test infrastructure, I'm happy to do that. Mike -- Michael Droettboom Science Software Branch Operations and Engineering Division Space Telescope Science Institute Operated by AURA for NASA -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf ___ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] Comparing pdf output in tests
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 of the test are converted using with exactly the >> same version of gs, there should be no font-rendering or antialiasing >> mismatches. >> >> Can we assume that all test computers will have some version of >> Ghostscript installed and callable as "gs"? >> >> > 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 don't know how different the output will be from different versions of > gs -- maybe we should just try it and see. I have a pretty old version > of gs on my RHEL4 box (7.07). If you want me to send you a png of a > particular pdf to directly compare with yours before you even start with > the test infrastructure, I'm happy to do that. > I understood Jouni's idea to be to save the .pdfs as baseline images -- then the same version of gs would be used to generated the rasterized images for the baseline and test result -- the version on your computer. I think this is the way to go (either that or compare the PDFs directly somehow). Anyhow, allowing the test infrastructure to support testing multiple backends is why I removed file extensions from the test image name in the first place, so anything along these lines should hopefully be quite doable. We could add a keyword arg to the image comparison decorator that specified which image formats to test. Alternatively, it could perform comparisons based on the presence baseline images of known extensions. -Andrew -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf ___ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
[matplotlib-devel] 0.99.1 and the setup.cfg file
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 tkagg. This is in direct contradiction to the text just above these commands, which say the default is an "auto" option. # You can uncomment any the following lines if you know you do # not want to use the GUI toolkit. Acceptible values are: # True: build the extension. Exits with a warning if the # required dependencies are not available # False: do not build the extension # auto: build if the required dependencies are available, # otherwise skip silently. This is the default # behavior # #gtk = False #gtkagg = False tkagg = True wxagg = True macosx = True [rc_options] # User-configurable options # # Default backend, one of: Agg, Cairo, CocoaAgg, GTK, GTKAgg, GTKCairo, # FltkAgg, MacOSX, Pdf, Ps, QtAgg, Qt4Agg, SVG, TkAgg, WX, WXAgg. # # The Agg, Ps, Pdf and SVG backends do not require external # dependencies. Do not choose GTK, GTKAgg, GTKCairo, MacOSX, TkAgg or WXAgg # if you have disabled the relevent extension modules. Agg will be used # by default. # backend = TkAgg Should I just delete the setup.cfg file? It looks like it shouldn't be in the release, since there is a template file there. Thanks, Jason -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf ___ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] 0.99.1 and the setup.cfg file
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 with it. We do ship setup.cfg.template which you can use to create and customize a setup.cfg, but there shouldn't be one by default. It's not listed in MANIFEST.in, but apparently when I built the tarball I had not done an svn-clean. setup.cfg *was* in my MANIFEST (which is autogenerated at build time) on my build machine, but I am not sure why it was added since it isn't in MANIFEST.in. In any case, I just rebuilt and reuploaded the tarball with no setup.cfg from a clean dir https://sourceforge.net/projects/matplotlib/files/matplotlib/matplotlib-0.99.1/ Thanks for the report. JDH -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf ___ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] Comparing pdf output in tests
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 baseline images -- > then the same version of gs would be used to generated the rasterized > images for the baseline and test result -- the version on your computer. > I think this is the way to go (either that or compare the PDFs directly > somehow). Yes, that's what I meant: we want to test that the PDF file generated by the code is "equivalent" to the baseline, and aside from some metadata in the files, I think "equivalence" should mean that the files generate the same rasterized output on some particular PDF renderer. I suppose Ghostscript is widespread enough that we can assume that it exists in the test environment? Or is there some buildout magic that we should add in some file? -- Jouni K. Seppänen http://www.iki.fi/jks -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf ___ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Re: [matplotlib-devel] Comparing pdf output in tests
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. >>> >>> >> I understood Jouni's idea to be to save the .pdfs as baseline images -- >> then the same version of gs would be used to generated the rasterized >> images for the baseline and test result -- the version on your computer. >> I think this is the way to go (either that or compare the PDFs directly >> somehow). >> > > Yes, that's what I meant: we want to test that the PDF file generated by > the code is "equivalent" to the baseline, and aside from some metadata > in the files, I think "equivalence" should mean that the files generate > the same rasterized output on some particular PDF renderer. > > I suppose Ghostscript is widespread enough that we can assume that it > exists in the test environment? Or is there some buildout magic that we > should add in some file? > We can always use "gs --version" in subprocess.check_call() and if it's not installed (or if there's some other error with it) just not compare the pdf output. That way we still test that the pdf generation at least doesn't raise an exception, and a test pdf is generated for later inspection if need be. Jouni - I don't think this would be hard to add, but I'm swamped at work. If this is an itch you'd like to scratch, feel free to hack away on the image_comparison() function in lib/matplotlib/testing/decorators.py -- it's a pretty straightforward piece of code. -Andrew -- Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf ___ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
