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
|
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
|
|
|
|
|
|
1
(5) |
2
(1) |
|
3
|
4
|
5
(1) |
6
(1) |
7
(9) |
8
(2) |
9
(7) |
|
10
(5) |
11
(5) |
12
(1) |
13
(4) |
14
(4) |
15
|
16
|
|
17
(1) |
18
|
19
|
20
|
21
(2) |
22
(2) |
23
|
|
24
(1) |
25
|
26
(1) |
27
|
28
(1) |
29
|
30
(16) |
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