matplotlib-devel Mailing List for matplotlib (Page 3)

Hey everyone,
I know many people follow both lists, but I just wanted to point to a
lively set of threads which contain "notebook plots via javascript" in
the subject.
it's split up into many separate conversations, so it's best to just
go to this page and then search around:
http://mail.scipy.org/pipermail/ipython-dev/2012-June/thread.html
The limitations and advantages of current solutions and possible
future directions (and possible future dead ends) have been discussed,
both in terms of MPL specifically, and in terms of alternatives.
-- 
Paul Ivanov
314 address only used for lists, off-list direct email at:
http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7

I have just merged in a rework of the transform invalidation mechanism
onto mpl master.
Throughout development it was clear that these changes can have wide
reaching and unexpected impacts on upstream code, as was highlighted
on more than one occasion when running the mpl unit tests.
Whilst I do not anticipate further issues, I am giving this heads up
just in case strange, possibly transform related, issues arise since
committing #723 (https://github.com/matplotlib/matplotlib/pull/723).
Debugging transform issues can get quite deep, so if you do come
across anything and want to share the burden I would be happy to help
if you can provide code to reproduce the issue.
Thanks,

I also want to flag PR #934 as something that should go into the rc. 
It's currently against master but it's important enough/simple enough 
that it should be backported.
Mike
On 06/07/2012 03:04 PM, John Hunter wrote:
> On Thu, Jun 7, 2012 at 1:55 PM, Eric Firing<ef...@ha...> wrote:
>
>> I did not see any replies to Sandro's reasonable question.
>>
>> Wasn't there at least a plan for a 1.1.x release soon?
>>
>> There are quite a few open pull requests for master--not many for
>> 1.1.x--but I don't know that any are blockers.
> There are no open issues tagged "release_candidate" so I'll go ahead
> and make the 1.1.x release if there are no objections.
>
> JDH
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

On 06/07/2012 05:44 PM, Eric Firing wrote:
> On 06/07/2012 09:04 AM, John Hunter wrote:
>> On Thu, Jun 7, 2012 at 1:55 PM, Eric Firing<ef...@ha...> wrote:
>>
>>> I did not see any replies to Sandro's reasonable question.
>>>
>>> Wasn't there at least a plan for a 1.1.x release soon?
>>>
>>> There are quite a few open pull requests for master--not many for
>>> 1.1.x--but I don't know that any are blockers.
>> There are no open issues tagged "release_candidate" so I'll go ahead
>> and make the 1.1.x release if there are no objections.
>>
>> JDH
> Point of information: running matplotlib/tests.py on linux with 1.1.x, I
> get 1 image comparison failure:
> failed-diff-mathfont_stix_14.png
>
> It is all a matter of subtle differences in horizontal placement, and to
> my eye, the spacing looks better with what I am getting than with the
> expected image.
>
> Is anyone else getting this failure? If so, maybe updating the expected
> image would take care of it. Otherwise, maybe the tolerance needs to be
> increased.
I'm not getting this error. Perhaps the tolerance should be increased 
or the acceptable range of freetype versions needs to be reduced.
Mike

On 6/7/2012 1:34 PM, Christoph Gohlke wrote:
>
>
> On 6/7/2012 1:01 PM, John Hunter wrote:
>> On Thu, Jun 7, 2012 at 2:57 PM, Christoph Gohlke <cg...@uc...> wrote:
>>
>>> Is there time for another release candidate?
>>>
>>> With the latest github branch on win-amd64-py2.7 I get both, a segfault
>>> and a test failure in "matplotlib.tests.test_text.test_font_styles.test".
>>
>> If you are getting a segfault, is there on the latest branch, would it
>> make sense to do an RC? It seems like we would want to fix the
>> segfault first. Can you give us more details on the segfault, eg
>> backend, conditions to reproduce, etc?
>>
>>
>
> There have been many changes since the last rc. The crash is probably
> related to very recent changes. Ideally the segfault should be fixed
> before rc2.
>
>
> The crash on win-amd64-py2.7 is with the PDF backend:
>
> Python 2.7.3 (default, Apr 10 2012, 23:24:47) [MSC v.1500 64 bit
> (AMD64)] on win32
>>>> import matplotlib as mpl
>>>> mpl.use("agg")
>>>> mpl.test(verbosity=2)
> <snip>
> matplotlib.tests.test_mathtext.mathtext_stixsans_65_test.test ... ok
> matplotlib.tests.test_mathtext.mathtext_stixsans_65_test.test ... ok
> matplotlib.tests.test_mathtext.mathtext_stixsans_65_test.test ...
> KNOWNFAIL: Cannot compare svg files on this system
> matplotlib.tests.test_mathtext.test_fontinfo ... ok
> matplotlib.tests.test_text.test_antialiasing.test ... ok
> matplotlib.tests.test_text.test_font_styles.test ... ok
> matplotlib.tests.test_text.test_font_styles.test ...
> crash
>
>
> On win32-py2.7 the test fails but doesn't crash. The failure is that
> bold font styles are not rendered bold:
>
> Python 2.7.3 (default, Apr 10 2012, 23:31:26) [MSC v.1500 32 bit
> (Intel)] on win32
> <snip>
> ======================================================================
> FAIL: matplotlib.tests.test_text.test_font_styles.test
> ----------------------------------------------------------------------
> Traceback (most recent call last):
> File "X:\Python27\lib\site-packages\nose\case.py", line 197, in runTest
> self.test(*self.arg)
> File
> "X:\Python27\lib\site-packages\matplotlib\testing\decorators.py", line
> 36, in failer
> result = f(*args, **kwargs)
> File
> "X:\Python27\lib\site-packages\matplotlib\testing\decorators.py", line
> 140, in do_test
> '(RMS %(rms).3f)'%err)
> ImageComparisonFailure: images not close:
> test\result_images\test_text\font_styles.png vs.
> test\result_images\test_text\expected-font_styles.png (RMS 47.138)
>
> ======================================================================
> FAIL: matplotlib.tests.test_text.test_font_styles.test
> ----------------------------------------------------------------------
> Traceback (most recent call last):
> File "X:\Python27\lib\site-packages\nose\case.py", line 197, in runTest
> self.test(*self.arg)
> File
> "X:\Python27\lib\site-packages\matplotlib\testing\decorators.py", line
> 36, in failer
> result = f(*args, **kwargs)
> File
> "X:\Python27\lib\site-packages\matplotlib\testing\decorators.py", line
> 140, in do_test
> '(RMS %(rms).3f)'%err)
> ImageComparisonFailure: images not close:
> test\result_images\test_text\font_styles_pdf.png vs.
> test\result_images\test_text\expected-font_styles_pdf.png (RMS 23.409)
>
> ----------------------------------------------------------------------
> Ran 1068 tests in 231.978s
>
> FAILED (KNOWNFAIL=268, failures=2)
>
>
> I'll file a ticket if I can't fix it using a debug build.
>
https://github.com/matplotlib/matplotlib/issues/933
Christoph

On 06/07/2012 09:04 AM, John Hunter wrote:
> On Thu, Jun 7, 2012 at 1:55 PM, Eric Firing<ef...@ha...> wrote:
>
>> I did not see any replies to Sandro's reasonable question.
>>
>> Wasn't there at least a plan for a 1.1.x release soon?
>>
>> There are quite a few open pull requests for master--not many for
>> 1.1.x--but I don't know that any are blockers.
>
> There are no open issues tagged "release_candidate" so I'll go ahead
> and make the 1.1.x release if there are no objections.
>
> JDH
Point of information: running matplotlib/tests.py on linux with 1.1.x, I 
get 1 image comparison failure:
failed-diff-mathfont_stix_14.png
It is all a matter of subtle differences in horizontal placement, and to 
my eye, the spacing looks better with what I am getting than with the 
expected image.
Is anyone else getting this failure? If so, maybe updating the expected 
image would take care of it. Otherwise, maybe the tolerance needs to be 
increased.

On 6/7/2012 1:01 PM, John Hunter wrote:
> On Thu, Jun 7, 2012 at 2:57 PM, Christoph Gohlke <cg...@uc...> wrote:
>
>> Is there time for another release candidate?
>>
>> With the latest github branch on win-amd64-py2.7 I get both, a segfault
>> and a test failure in "matplotlib.tests.test_text.test_font_styles.test".
>
> If you are getting a segfault, is there on the latest branch, would it
> make sense to do an RC? It seems like we would want to fix the
> segfault first. Can you give us more details on the segfault, eg
> backend, conditions to reproduce, etc?
>
>
There have been many changes since the last rc. The crash is probably 
related to very recent changes. Ideally the segfault should be fixed 
before rc2.
The crash on win-amd64-py2.7 is with the PDF backend:
Python 2.7.3 (default, Apr 10 2012, 23:24:47) [MSC v.1500 64 bit 
(AMD64)] on win32
>>> import matplotlib as mpl
>>> mpl.use("agg")
>>>mpl.test(verbosity=2)
<snip>
matplotlib.tests.test_mathtext.mathtext_stixsans_65_test.test ... ok
matplotlib.tests.test_mathtext.mathtext_stixsans_65_test.test ... ok
matplotlib.tests.test_mathtext.mathtext_stixsans_65_test.test ... 
KNOWNFAIL: Cannot compare svg files on this system
matplotlib.tests.test_mathtext.test_fontinfo ... ok
matplotlib.tests.test_text.test_antialiasing.test ... ok
matplotlib.tests.test_text.test_font_styles.test ... ok
matplotlib.tests.test_text.test_font_styles.test ...
crash
On win32-py2.7 the test fails but doesn't crash. The failure is that 
bold font styles are not rendered bold:
Python 2.7.3 (default, Apr 10 2012, 23:31:26) [MSC v.1500 32 bit 
(Intel)] on win32
<snip>
======================================================================
FAIL: matplotlib.tests.test_text.test_font_styles.test
----------------------------------------------------------------------
Traceback (most recent call last):
 File "X:\Python27\lib\site-packages\nose\case.py", line 197, in runTest
 self.test(*self.arg)
 File 
"X:\Python27\lib\site-packages\matplotlib\testing\decorators.py", line 
36, in failer
 result = f(*args, **kwargs)
 File 
"X:\Python27\lib\site-packages\matplotlib\testing\decorators.py", line 
140, in do_test
 '(RMS %(rms).3f)'%err)
ImageComparisonFailure: images not close: 
test\result_images\test_text\font_styles.png vs.
 test\result_images\test_text\expected-font_styles.png (RMS 47.138)
======================================================================
FAIL: matplotlib.tests.test_text.test_font_styles.test
----------------------------------------------------------------------
Traceback (most recent call last):
 File "X:\Python27\lib\site-packages\nose\case.py", line 197, in runTest
 self.test(*self.arg)
 File 
"X:\Python27\lib\site-packages\matplotlib\testing\decorators.py", line 
36, in failer
 result = f(*args, **kwargs)
 File 
"X:\Python27\lib\site-packages\matplotlib\testing\decorators.py", line 
140, in do_test
 '(RMS %(rms).3f)'%err)
ImageComparisonFailure: images not close: 
test\result_images\test_text\font_styles_pdf.png vs.
 test\result_images\test_text\expected-font_styles_pdf.png (RMS 23.409)
----------------------------------------------------------------------
Ran 1068 tests in 231.978s
FAILED (KNOWNFAIL=268, failures=2)
I'll file a ticket if I can't fix it using a debug build.
Christoph

On Thu, Jun 7, 2012 at 2:57 PM, Christoph Gohlke <cg...@uc...> wrote:
> Is there time for another release candidate?
>
> With the latest github branch on win-amd64-py2.7 I get both, a segfault
> and a test failure in "matplotlib.tests.test_text.test_font_styles.test".
If you are getting a segfault, is there on the latest branch, would it
make sense to do an RC? It seems like we would want to fix the
segfault first. Can you give us more details on the segfault, eg
backend, conditions to reproduce, etc?

On 6/7/2012 12:04 PM, John Hunter wrote:
> On Thu, Jun 7, 2012 at 1:55 PM, Eric Firing <ef...@ha...> wrote:
>
>> I did not see any replies to Sandro's reasonable question.
>>
>> Wasn't there at least a plan for a 1.1.x release soon?
>>
>> There are quite a few open pull requests for master--not many for
>> 1.1.x--but I don't know that any are blockers.
>
> There are no open issues tagged "release_candidate" so I'll go ahead
> and make the 1.1.x release if there are no objections.
>
> JDH
>
Is there time for another release candidate?
With the latest github branch on win-amd64-py2.7 I get both, a segfault 
and a test failure in "matplotlib.tests.test_text.test_font_styles.test".
Christoph

On Thu, Jun 7, 2012 at 1:55 PM, Eric Firing <ef...@ha...> wrote:
> I did not see any replies to Sandro's reasonable question.
>
> Wasn't there at least a plan for a 1.1.x release soon?
>
> There are quite a few open pull requests for master--not many for
> 1.1.x--but I don't know that any are blockers.
There are no open issues tagged "release_candidate" so I'll go ahead
and make the 1.1.x release if there are no objections.
JDH

On 06/02/2012 10:38 AM, Sandro Tosi wrote:
> Hello,
>
> On Sat, May 12, 2012 at 11:56 AM, Sandro Tosi<mo...@de...> wrote:
>> Hello,
>> as you may be aware of, in 1 month (more or less) Debian will freeze,
>> that means that no new upstream releases will be allowed in the
>> upcoming release, only fixex for important bugs.
>
> Sorry to keep revamping this, but Debian freeze will be in about 2
> weeks: do you have in mind a date for a matplotlib release?
>
> Cheers.
I did not see any replies to Sandro's reasonable question.
Wasn't there at least a plan for a 1.1.x release soon?
There are quite a few open pull requests for master--not many for 
1.1.x--but I don't know that any are blockers.
Eric

Hi matplotlib developers,
this is my first commit to matplotlib. I am using it heavily in a 
scientific context. I followed the How-to and send you an according 
patch for what I consider a bug. If it doesn't make sense, please be 
lenient with me for now, since it my first time. : )
As described in the subject line, I made the alpha keyword in the 
errorbar command act also on the error bars and not only on the markers. 
The previous behaviour seemed inconsistent.
Cheers,
Hans

I've come across a problem (possibly a bug in cleanup_path) after
plotting a line containing nan's and then scaling the axes so that the
line is clipped by the axes.
Instead of a gap at the position of the nan value, two extra segments
appear - back to the start and then onto the next-plus-one valid
point. It's quite dependent on exactly how the line is clipped, and
by interactively zooming the plot the issue can be made to disappear
and reappear.
e.g.
##############################
import matplotlib
matplotlib.use('pdf') #pdf or ps or agg (incl. inside gui) reproduce
the issue, cairo works as expected
import matplotlib.pyplot as plt
import numpy as np
f = plt.figure()
ax = f.add_subplot(111)
ax.plot([30.,50.,900.,449.0,np.nan,50,60,100])
ax.set_ylim([0,400]) #default plot limits work fine
f.savefig('test')
##############################
This is with the Ubuntu 12.04 version of matplotlib (on x86_64);
v1.1.1rc. Version 1.0.1 (also via Ubuntu) was ok.
For the pdf backend, at least, the problem seems to appear in the call to
cleanup_path at line 247 of path.py (in iter_segments):
vertices, codes = cleanup_path(self, transform, remove_nans, clip,
 snap, stroke_width, simplify, curves)
Before the call, the path looks ok, but after the call to
cleanup_path, vertices is a bit of a mess (corresponding 'code' in
brackets):
 array([[ 72. , 69.12 ], (moveto)
 [ 135.77142857, 86.4 ], (lineto)
 [ 165.86834734, 433. ], (lineto)
 [ 263.00922817, 433. ], (moveto)
 [ 263.31428571, 431.136 ], (lineto)
 [ 72. , 69.12 ], (lineto) <--- (should be a gap?)
 [ 454.62857143, 95.04 ], (lineto)
 [ 518.4 , 129.6 ], (lineto)
 [ 518.4 , 129.6 ]]) (stop)
I can work around the problem by setting the backend to 'cairo' or by adding
 clip = None
near the top of iter_segments (line 235 of path.py)
HTH.

Hello,
On Sat, May 12, 2012 at 11:56 AM, Sandro Tosi <mo...@de...> wrote:
> Hello,
> as you may be aware of, in 1 month (more or less) Debian will freeze,
> that means that no new upstream releases will be allowed in the
> upcoming release, only fixex for important bugs.
Sorry to keep revamping this, but Debian freeze will be in about 2
weeks: do you have in mind a date for a matplotlib release?
Cheers.
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

On 06/01/2012 06:21 AM, Michael Droettboom wrote:
> Ideally, the example would be both:
>
> 1) standalone under the examples tree so that it creates a gallery
> entry in the docs
It doesn't have to be a new example, it can be a modification of an 
existing example. Examples are good, but too many can become 
overwhelming. The gallery needs pruning and additional organization, as 
has been discussed before.
Eric

Ideally, the example would be both:
 1) standalone under the examples tree so that it creates a gallery 
entry in the docs
 2) a regression test so that testing will ensure the feature 
continues to work over time
This isn't true of every PR, obviously, but for things that create nice 
new visible features it's a good rule of thumb.
Mike
On 06/01/2012 11:55 AM, Paul Hobson wrote:
> Question about this:
>
> Do you want the example in the docstring of the function or just a
> standalone script that you can run to verify that the PR actually
> works?
> (My PR will have to wait until tonight, unfortunately)
> -paul
>
> On Fri, Jun 1, 2012 at 8:37 AM, Michael Droettboom<md...@st...> wrote:
>> As you probably know, we've got a lot of pull requests in the hopper.
>> Thanks to everyone who's been triaging these lately.
>>
>> I've just gone through and tried to add comments about what's left to be
>> done with each to make them mergeable. (9 times out of 10, I'm saying
>> "add an example and unit test" ;) If you submitted a PR that you feel
>> is being ignored, feel free to ping those involved by adding a comment
>> to the end of the PR that summarizes what issues are remaining.
>>
>> Mike
>>
>> ------------------------------------------------------------------------------
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond. Discussions
>> will include endpoint security, mobile security and the latest in malware
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> _______________________________________________
>> Matplotlib-devel mailing list
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

As you probably know, we've got a lot of pull requests in the hopper. 
Thanks to everyone who's been triaging these lately.
I've just gone through and tried to add comments about what's left to be 
done with each to make them mergeable. (9 times out of 10, I'm saying 
"add an example and unit test" ;) If you submitted a PR that you feel 
is being ignored, feel free to ping those involved by adding a comment 
to the end of the PR that summarizes what issues are remaining.
Mike

Just wanted to draw attention to some platform-specific pull requests 
that need some third-party testing and comments from people on OS-X and 
MS-Windows. If you're running on one of those platforms and able to 
build from git branches, it would be great to have some input:
OS-X:
Updates to the build script:
https://github.com/matplotlib/matplotlib/pull/899
Adding an icon for Tkinter, Gtk, Wx:
https://github.com/matplotlib/matplotlib/pull/897 
<https://github.com/matplotlib/matplotlib/pull/899>
Getting the filename from the window title:
https://github.com/matplotlib/matplotlib/pull/908
MS-Windows:
Adding an icon for Tkinter, Gtk, Wx:
https://github.com/matplotlib/matplotlib/pull/897 
<https://github.com/matplotlib/matplotlib/pull/899>
Getting the filename from the window title:
https://github.com/matplotlib/matplotlib/pull/908
Mike

Welcome aboard, Phil!
Regards,
-JJ
On Thu, May 31, 2012 at 8:55 PM, John Hunter <jd...@gm...> wrote:
> Phil Elson has been making pull requests for some time now on matters
> great and small, from hairy transformations improvements to minor
> docstring cleanups to GUI fixes. Given his prolific work, I thought
> it would be suitable to recognize him as a core matplotlib developer
> by adding him to the github organization. While the distributed
> nature of the github system blurs the line between official and
> regular developers, it is helpful to recognize those who make frequent
> quality contributions and give them the permissions to merge pull
> requests into the main repo.
>
> Thanks for all your help Phil, and welcome aboard.
>
> JDH
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel