[matplotlib-devel] building matplotlib-0.99.1.1.tar.gz on Mac OS X 10.6.1 (Snow Leopard)

2009-10-12 Thread Daniel Huff
Hello, With the caveat that I have not closely followed this mail list, I thought I would offer an alternate build method than what seems to be the preferred method for building matplotlib on Mac OS X. I tried to skim through recent mailing list posts to see if anything like this had been

Re: [matplotlib-devel] Problem adding a new test

2009-10-12 Thread Michael Droettboom
I've committed support for comparing SVG files using Inkscape and verifying them against the official SVG DTD using xmllint. Michael Droettboom wrote: > Andrew Straw wrote: > >> Done in r7863. To make use of it, do something like the following patch >> (and don't forget to delete the baseline

Re: [matplotlib-devel] Problem adding a new test

2009-10-12 Thread Andrew Straw
Michael Droettboom wrote: > I've committed support for comparing SVG files using Inkscape and > verifying them against the official SVG DTD using xmllint. > Man, are we standards compliant around here or what? :) Cool. > Michael Droettboom wrote: > >> Andrew Straw wrote: >> >> >>> D

Re: [matplotlib-devel] pylab.imshow() does not handle clip_path properly

2009-10-12 Thread Andrew Straw
Gellule Xg wrote: >>> This is a bug report for matplotlib version 0.99.1.1 >>> >>> The clip_path keyword of imshow() does not work when setting it to >>> (Path, Transform) for two reasons: >>> >> Hi, Thanks for the report. Do you have a simple test script that we can >> use to see the probl

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

2009-10-12 Thread Andrew Straw
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] Problem adding a new test

2009-10-12 Thread Andrew Straw
Michael Droettboom wrote: > I've committed support for comparing SVG files using Inkscape and > verifying them against the official SVG DTD using xmllint. I just noticed the test_axes/hexbin_extent.svg baseline image is more than 5 MB. I wonder if we can somehow simplify the svg generated to re

Re: [matplotlib-devel] Problem adding a new test

2009-10-12 Thread Michael Droettboom
I suspect for that one we can just do without it. It isn't really testing anything SVG-specific. Mike Andrew Straw wrote: > Michael Droettboom wrote: >> I've committed support for comparing SVG files using Inkscape and >> verifying them against the official SVG DTD using xmllint. > I just not

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

2009-10-12 Thread Jouni K . Seppänen
Andrew Straw writes: > Sorry for not noticing this earlier, but I'm looking in the baseline > image directory, and I see a bunch of *_pdf.png files. I guess these > have been convered to png from pdf on the tester's machine. Do you think > it makes more sense to have the .pdf files in the test

Re: [matplotlib-devel] Problem adding a new test

2009-10-12 Thread Jouni K . Seppänen
Andrew Straw writes: > I just noticed the test_axes/hexbin_extent.svg baseline image is more > than 5 MB. I wonder if we can somehow simplify the svg generated to > reduce the file size or if we should perhaps just not do the svg > extension on this test? How about keeping them gzipped? If yo

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

2009-10-12 Thread Andrew Straw
Jouni K. Seppänen wrote: > Andrew Straw writes: > > >> Sorry for not noticing this earlier, but I'm looking in the baseline >> image directory, and I see a bunch of *_pdf.png files. I guess these >> have been convered to png from pdf on the tester's machine. Do you think >> it makes more sen