You can subscribe to this list here.
2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(33) |
Dec
(20) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2004 |
Jan
(7) |
Feb
(44) |
Mar
(51) |
Apr
(43) |
May
(43) |
Jun
(36) |
Jul
(61) |
Aug
(44) |
Sep
(25) |
Oct
(82) |
Nov
(97) |
Dec
(47) |
2005 |
Jan
(77) |
Feb
(143) |
Mar
(42) |
Apr
(31) |
May
(93) |
Jun
(93) |
Jul
(35) |
Aug
(78) |
Sep
(56) |
Oct
(44) |
Nov
(72) |
Dec
(75) |
2006 |
Jan
(116) |
Feb
(99) |
Mar
(181) |
Apr
(171) |
May
(112) |
Jun
(86) |
Jul
(91) |
Aug
(111) |
Sep
(77) |
Oct
(72) |
Nov
(57) |
Dec
(51) |
2007 |
Jan
(64) |
Feb
(116) |
Mar
(70) |
Apr
(74) |
May
(53) |
Jun
(40) |
Jul
(519) |
Aug
(151) |
Sep
(132) |
Oct
(74) |
Nov
(282) |
Dec
(190) |
2008 |
Jan
(141) |
Feb
(67) |
Mar
(69) |
Apr
(96) |
May
(227) |
Jun
(404) |
Jul
(399) |
Aug
(96) |
Sep
(120) |
Oct
(205) |
Nov
(126) |
Dec
(261) |
2009 |
Jan
(136) |
Feb
(136) |
Mar
(119) |
Apr
(124) |
May
(155) |
Jun
(98) |
Jul
(136) |
Aug
(292) |
Sep
(174) |
Oct
(126) |
Nov
(126) |
Dec
(79) |
2010 |
Jan
(109) |
Feb
(83) |
Mar
(139) |
Apr
(91) |
May
(79) |
Jun
(164) |
Jul
(184) |
Aug
(146) |
Sep
(163) |
Oct
(128) |
Nov
(70) |
Dec
(73) |
2011 |
Jan
(235) |
Feb
(165) |
Mar
(147) |
Apr
(86) |
May
(74) |
Jun
(118) |
Jul
(65) |
Aug
(75) |
Sep
(162) |
Oct
(94) |
Nov
(48) |
Dec
(44) |
2012 |
Jan
(49) |
Feb
(40) |
Mar
(88) |
Apr
(35) |
May
(52) |
Jun
(69) |
Jul
(90) |
Aug
(123) |
Sep
(112) |
Oct
(120) |
Nov
(105) |
Dec
(116) |
2013 |
Jan
(76) |
Feb
(26) |
Mar
(78) |
Apr
(43) |
May
(61) |
Jun
(53) |
Jul
(147) |
Aug
(85) |
Sep
(83) |
Oct
(122) |
Nov
(18) |
Dec
(27) |
2014 |
Jan
(58) |
Feb
(25) |
Mar
(49) |
Apr
(17) |
May
(29) |
Jun
(39) |
Jul
(53) |
Aug
(52) |
Sep
(35) |
Oct
(47) |
Nov
(110) |
Dec
(27) |
2015 |
Jan
(50) |
Feb
(93) |
Mar
(96) |
Apr
(30) |
May
(55) |
Jun
(83) |
Jul
(44) |
Aug
(8) |
Sep
(5) |
Oct
|
Nov
(1) |
Dec
(1) |
2016 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
(3) |
Sep
(1) |
Oct
(3) |
Nov
|
Dec
|
2017 |
Jan
|
Feb
(5) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(3) |
Aug
|
Sep
(7) |
Oct
|
Nov
|
Dec
|
2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: John H. <jd...@gm...> - 2012-06-10 02:13:15
|
Thanks -- I've already started the process for the files, but can you test upload something into the 1.1 folder (easy to subsequently delete). I just made you a project admin. I'd like to get this figure out eventually! On Sat, Jun 9, 2012 at 8:53 PM, Christoph Gohlke <cg...@uc...> wrote: > Hi John, > > the matplotlib-1.1.1rc2.win installers are at > <http://www.lfd.uci.edu/~gohlke/pythonlibs/#matplotlib>. I am again unable > to upload them to SF. > > They are built against numpy 1.6.2 and include the test files. All tests > pass on Python 2.7, 32 and 64 bit. > > Christoph > > > > On 6/9/2012 2:14 PM, John Hunter wrote: >> >> I just uploaded the v1.1.1rc2 tarballs to the sourceforge site >> >> >> https://sourceforge.net/projects/matplotlib/files/matplotlib/matplotlib-1.1.1/ >> >> As soon as we get binaries, I'll send out another call for testing on >> the users list. Russell and Christoph, easiest if you just upload the >> binaries directly. You should both have permissions on the sf site. >> >> A copy of the site docs are available at >> http://matplotlib.sourceforge.net/rc/v1.1.1rc2/ >> >> > |
From: Christoph G. <cg...@uc...> - 2012-06-10 01:53:54
|
Hi John, the matplotlib-1.1.1rc2.win installers are at <http://www.lfd.uci.edu/~gohlke/pythonlibs/#matplotlib>. I am again unable to upload them to SF. They are built against numpy 1.6.2 and include the test files. All tests pass on Python 2.7, 32 and 64 bit. Christoph On 6/9/2012 2:14 PM, John Hunter wrote: > I just uploaded the v1.1.1rc2 tarballs to the sourceforge site > > https://sourceforge.net/projects/matplotlib/files/matplotlib/matplotlib-1.1.1/ > > As soon as we get binaries, I'll send out another call for testing on > the users list. Russell and Christoph, easiest if you just upload the > binaries directly. You should both have permissions on the sf site. > > A copy of the site docs are available at > http://matplotlib.sourceforge.net/rc/v1.1.1rc2/ > > |
From: Benjamin R. <ben...@ou...> - 2012-06-10 01:52:59
|
Don't forget to tag the rc in git! On Sat, Jun 9, 2012 at 6:40 PM, John Hunter <jd...@gm...> wrote: > On Sat, Jun 9, 2012 at 5:33 PM, John Hunter <jd...@gm...> wrote: > > On Sat, Jun 9, 2012 at 5:27 PM, Eric Firing <ef...@ha...> wrote: > >> It also has backend_gdk.c (supposed to be a temporary copy of > >> _backend_gdk.c) and some others like it. > > > > OK, I'll rebuild them super clean... I know what went wrong. > > Just uploaded two new files built from clean git checkouts. > > > ------------------------------------------------------------------------------ > 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 > |
From: John H. <jd...@gm...> - 2012-06-09 22:40:53
|
On Sat, Jun 9, 2012 at 5:33 PM, John Hunter <jd...@gm...> wrote: > On Sat, Jun 9, 2012 at 5:27 PM, Eric Firing <ef...@ha...> wrote: >> It also has backend_gdk.c (supposed to be a temporary copy of >> _backend_gdk.c) and some others like it. > > OK, I'll rebuild them super clean... I know what went wrong. Just uploaded two new files built from clean git checkouts. |
From: John H. <jd...@gm...> - 2012-06-09 22:33:40
|
On Sat, Jun 9, 2012 at 5:27 PM, Eric Firing <ef...@ha...> wrote: > It also has backend_gdk.c (supposed to be a temporary copy of > _backend_gdk.c) and some others like it. OK, I'll rebuild them super clean... I know what went wrong. |
From: Eric F. <ef...@ha...> - 2012-06-09 22:27:17
|
On 06/09/2012 12:21 PM, John Hunter wrote: > On Sat, Jun 9, 2012 at 5:11 PM, Eric Firing<ef...@ha...> wrote: >> On 06/09/2012 11:14 AM, John Hunter wrote: >>> I just uploaded the v1.1.1rc2 tarballs to the sourceforge site >> >> John, >> >> Is it intentional that the tarballs include doc/build? > > It isn't intentional and it looks like it only affected the "notests" > dist. Fixed it -- thanks for catching it. It also has backend_gdk.c (supposed to be a temporary copy of _backend_gdk.c) and some others like it. Which raises the question: why are these temporary copies needed at all? I don't see any explanation in setupext.py. I imagine it has to do with how some systems handle the leading underscore on the name, but it would be nice to have it explained in a comment in setupext.py. Eric |
From: John H. <jd...@gm...> - 2012-06-09 22:21:28
|
On Sat, Jun 9, 2012 at 5:11 PM, Eric Firing <ef...@ha...> wrote: > On 06/09/2012 11:14 AM, John Hunter wrote: >> I just uploaded the v1.1.1rc2 tarballs to the sourceforge site > > John, > > Is it intentional that the tarballs include doc/build? It isn't intentional and it looks like it only affected the "notests" dist. Fixed it -- thanks for catching it. |
From: Eric F. <ef...@ha...> - 2012-06-09 22:11:33
|
On 06/09/2012 11:14 AM, John Hunter wrote: > I just uploaded the v1.1.1rc2 tarballs to the sourceforge site John, Is it intentional that the tarballs include doc/build? Eric > > https://sourceforge.net/projects/matplotlib/files/matplotlib/matplotlib-1.1.1/ > > As soon as we get binaries, I'll send out another call for testing on > the users list. Russell and Christoph, easiest if you just upload the > binaries directly. You should both have permissions on the sf site. > > A copy of the site docs are available at > http://matplotlib.sourceforge.net/rc/v1.1.1rc2/ > > ------------------------------------------------------------------------------ > 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 |
From: John H. <jd...@gm...> - 2012-06-09 21:14:52
|
I just uploaded the v1.1.1rc2 tarballs to the sourceforge site https://sourceforge.net/projects/matplotlib/files/matplotlib/matplotlib-1.1.1/ As soon as we get binaries, I'll send out another call for testing on the users list. Russell and Christoph, easiest if you just upload the binaries directly. You should both have permissions on the sf site. A copy of the site docs are available at http://matplotlib.sourceforge.net/rc/v1.1.1rc2/ |
From: Jouni K. S. <jk...@ik...> - 2012-06-09 19:24:29
|
Alan Griffiths <ala...@gm...> writes: > 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. This sounds a lot like https://github.com/matplotlib/matplotlib/issues/804 There was a bug in the fix for that, which was fixed in https://github.com/matplotlib/matplotlib/pull/873 I think at least the latter fix was merged later than the release candidate was announced. You might want to try a later version. -- Jouni K. Seppänen http://www.iki.fi/jks |
From: Paul I. <piv...@gm...> - 2012-06-08 23:14:50
|
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 |
From: Phil E. <pel...@gm...> - 2012-06-08 17:41:11
|
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, |
From: Michael D. <md...@st...> - 2012-06-07 23:57:14
|
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 |
From: Michael D. <md...@st...> - 2012-06-07 23:37:17
|
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 |
From: Christoph G. <cg...@uc...> - 2012-06-07 22:54:40
|
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 |
From: Eric F. <ef...@ha...> - 2012-06-07 21:44:46
|
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. |
From: Christoph G. <cg...@uc...> - 2012-06-07 20:34:54
|
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 |
From: John H. <jd...@gm...> - 2012-06-07 20:02:07
|
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? |
From: Christoph G. <cg...@uc...> - 2012-06-07 19:57:40
|
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 |
From: John H. <jd...@gm...> - 2012-06-07 19:04:42
|
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 |
From: Eric F. <ef...@ha...> - 2012-06-07 18:56:12
|
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 |
From: Hans D. <han...@ki...> - 2012-06-06 15:57:45
|
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 |
From: Alan G. <ala...@gm...> - 2012-06-05 02:27:16
|
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. |
From: Sandro T. <mo...@de...> - 2012-06-02 20:39:27
|
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 |
From: Eric F. <ef...@ha...> - 2012-06-01 19:08:47
|
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 |