I must be missing something obvious, but I tried to add a new module
to lib/matplotlib/tests called test_image, which has a single method
so far, test_image_interps. I added the standard decorator and
baseline image, and I can see it being installed in the stdio on the
sage buildbot
http://mpl-bu
I've been only skimming the surface of the discussion about the new test
framework up until now.
Just got around to trying it, and every comparison failed because it was
selecting a different font than that used in the baseline images. (My
matplotlibrc customizes the fonts).
It seems we sho
The EMF backend of matplotlib is broken, which is a real problem if you want to
put matplotlib vector graphics into MS Word documents. I have just released a
patch which fixes the backend providing the basic features required, such as
drawing paths and texts in different styles and respecting cl
John Hunter wrote:
> I must be missing something obvious, but I tried to add a new module
> to lib/matplotlib/tests called test_image, which has a single method
> so far, test_image_interps. I added the standard decorator and
> baseline image, and I can see it being installed in the stdio on the
>
On Tue, Sep 8, 2009 at 10:14 AM, Andrew Straw wrote:
>> but I do not see an additional test being run (I still get the usual
>> 26 tests). Is there another step to getting this to be picked up by
>> the test harness?
>>
>
> As described in the "Creating a new module in matplotlib.tests" of the
>
On Tue, Sep 8, 2009 at 8:54 AM, Michael Droettboom wrote:
> I've been only skimming the surface of the discussion about the new test
> framework up until now.
>
> Just got around to trying it, and every comparison failed because it was
> selecting a different font than that used in the baseline ima
On 09/08/2009 10:24 AM, John Hunter wrote:
> On Tue, Sep 8, 2009 at 8:54 AM, Michael Droettboom wrote:
>
>> I've been only skimming the surface of the discussion about the new test
>> framework up until now.
>>
>> Just got around to trying it, and every comparison failed because it was
>> sele
On Tue, Sep 8, 2009 at 11:46 AM, Andrew Straw wrote:
> Michael Droettboom wrote:
>> On 09/08/2009 10:24 AM, John Hunter wrote:
>>
>>> On Tue, Sep 8, 2009 at 8:54 AM, Michael Droettboom wrote:
>>>
>>>
I've been only skimming the surface of the discussion about the new test
framework up un
John Hunter wrote:
> 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?
I have a presentation to give tomorrow, so I'd just as soon let you an
Interesting result. I pulled all of the new "actual" files from the 21
failing tests on the buildbots to my local machine and all of those
tests now pass for me. Good. Interestingly, there are still two tests
failing on my machine which did not fail on the buildbots, so I can't
grab the buil
Michael Droettboom wrote:
> Doing so, my results are even *less* in agreement with the baseline, but
> the real question is whether my results are in agreement with those on
> the buildbot machines with this change to forcibly turn hinting off. I
> should no pretty quickly when the buildbots st
On Tue, Sep 8, 2009 at 10:46 AM, Andrew Straw 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-defa
Michael Droettboom wrote:
> On 09/08/2009 10:24 AM, John Hunter wrote:
>
>> On Tue, Sep 8, 2009 at 8:54 AM, Michael Droettboom wrote:
>>
>>
>>> I've been only skimming the surface of the discussion about the new test
>>> framework up until now.
>>>
>>> Just got around to trying it, and
On Tue, Sep 8, 2009 at 11:47 AM, Michael Droettboom wrote:
> Interesting result. I pulled all of the new "actual" files from the 21
> failing tests on the buildbots to my local machine and all of those tests
> now pass for me. Good. Interestingly, there are still two tests failing on
> my machin
On Tue, Sep 8, 2009 at 12:34 PM, Andrew Straw wrote:
> Michael Droettboom wrote:
>> More information after another build iteration.
>>
>> The two tests that failed after updating to the unhinted images were
>> subtests of tests that were failing earlier. If a single test
>> function outputs multip
John Hunter wrote:
> I wrote a script at scipy when Andrew and I worked on this to
> recursively move known good actuals into the baselines directory, with
> some yes/no prompting, but it looks like it did not survive the test
> code migration, so we may want to develop something to replace it.
Yes
More information after another build iteration.
The two tests that failed after updating to the unhinted images were
subtests of tests that were failing earlier. If a single test function
outputs multiple images, image comparison stops after the first
mismatched image. So there's nothing pecu
John Hunter wrote:
> On Tue, Sep 8, 2009 at 12:34 PM, Andrew Straw wrote:
>
>> Michael Droettboom wrote:
>>
>>> More information after another build iteration.
>>>
>>> The two tests that failed after updating to the unhinted images were
>>> subtests of tests that were failing earlier. If a
Michael Droettboom wrote:
> Interesting result. I pulled all of the new "actual" files from the 21
> failing tests on the buildbots to my local machine and all of those
> tests now pass for me. Good. Interestingly, there are still two tests
> failing on my machine which did not fail on the bu
Michael Droettboom wrote:
> More information after another build iteration.
>
> The two tests that failed after updating to the unhinted images were
> subtests of tests that were failing earlier. If a single test
> function outputs multiple images, image comparison stops after the
> first mismatch
Hello,
The thread switches will be gone by the release of the new IPython. I am
assuming that some extra work needs to be done on both sides in preparation
to the new release. See the following test cases:
### This one locks the IPython unless the figure window is killed. If you do
an additional
Hey Gokhan,
thanks for the summary.
On Tue, Sep 8, 2009 at 12:45 PM, Gökhan Sever wrote:
> ### In a new IPython, these lines work --no locking after plt.show() "-a"
> makes the difference.
>
> I[1]: import matplotlib.pyplot as plt
>
> I[2]: %gui -a qt
> O[2]:
>
> I[3]: plt.plot(range(10))
> O[3
You also may need to do:
plt.interactive(True)
Cheers,
Brian
On Tue, Sep 8, 2009 at 12:45 PM, Gökhan Sever wrote:
> Hello,
>
> The thread switches will be gone by the release of the new IPython. I am
> assuming that some extra work needs to be done on both sides in preparation
> to the new re
Howdy,
The Qt4 backend appears to be broken in the Mac py2.6 binaries, using
OS X 10.5.7 and the latest version of the Qt SDK from qt.nokia.com. I
don't have the machine handy right this second but using plot() from
an IPython interpreter with my backend set to Qt4Agg causes a hard
crash f
On Tue, Sep 8, 2009 at 5:57 PM, David Warde-Farley wrote:
> Howdy,
>
> The Qt4 backend appears to be broken in the Mac py2.6 binaries, using
> OS X 10.5.7 and the latest version of the Qt SDK from qt.nokia.com. I
> don't have the machine handy right this second but using plot() from
> an IPython in
Hi Darren,
On 8-Sep-09, at 7:16 PM, Darren Dale wrote:
> I would be very surprised if this is due to the backend. More likely a
> mismatch between sip and pyqt versions.
I actually grabbed both of them yesterday from
riverbankcomputing.co.uk, PyQt-4.5.4 and sip-4.8.2. Is it possible
that th
26 matches
Mail list logo
