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
(1) |
|
2
|
3
(3) |
4
(2) |
5
(4) |
6
|
7
(5) |
8
|
|
9
(4) |
10
(8) |
11
|
12
(5) |
13
(4) |
14
(3) |
15
|
|
16
(1) |
17
(10) |
18
(3) |
19
(2) |
20
(10) |
21
(9) |
22
(4) |
|
23
|
24
(12) |
25
(2) |
26
(3) |
27
(8) |
28
(2) |
29
(4) |
|
30
(3) |
|
|
|
|
|
|
|
From: Christoph G. <cg...@uc...> - 2012-09-12 17:36:16
|
On 9/12/2012 10:31 AM, Christoph Gohlke wrote: > On 9/12/2012 7:44 AM, Michael Droettboom wrote: >> I have tagged and created a tarball for 1.2.0rc1. The githash is >> bda6dd9feab8. The tarball is on the github download page here: >> >> https://github.com/matplotlib/matplotlib/downloads >> >> I have created a new branch, v1.2.x, for continuing 1.2.x development. >> The feature freeze on master is now lifted and big experimental changes >> can be merged into master. Any bugfixes that need to go into 1.2.x >> should be merged into both places. Please mark any PRs for the 1.2.x >> branch with the 1.2.x milestone so we can verify that things are merged >> in both places. >> >> For those creating the Windows and Macintosh builds, let's try using the >> github download page rather than the one at Sourceforge this time. It >> is a lot simpler. >> >> For those creating distro packages, now is a good time to let us know >> what can be done to make the inclusion of matplotlib 1.2.0 as smooth as >> possible. >> >> Once the binaries are available, I will make an announcement to >> matplotlib-users. >> >> Mike >> >> > > Can we hold the Windows binaries until rc2? Setup.py corrupts the pytz > package, leading to stack-overflows on Python 3 and other problems on > Python 2. > > Christoph > Sorry, I meant the dateutil package, not pytz. Christoph |
|
From: Pierre H. <pie...@cr...> - 2012-09-12 17:35:36
|
Le 10/09/2012 19:19, Pierre Haessig a écrit : > Hello, > > This may be a silly question, but I'm wondering what happens in > Matplotlib rendering when there is a "big" Line2D object (say 10**7 > points) added to an Axes, with *visibility set to false*. > > [...] Hello, I was just wondering if I should preferably post such messages about a possible bug report on matplotlib-users mailing list instead of the devel ml. I'm not familiar with the community convention of how to spit topics between those two. Or is it better if I just report directly an issue on GitHub and start discussion from there ? Best, Pierre PS : an unrelated question about mailing list : I noticed that the matplotlib-users ml archive on sourceforge seems to stop from recording starting around July 16th 2012 http://sourceforge.net/mailarchive/forum.php?forum_name=matplotlib-users (on the other hand, the devel archive seems fine). No messages appear for August and September |
|
From: Christoph G. <cg...@uc...> - 2012-09-12 17:31:36
|
On 9/12/2012 7:44 AM, Michael Droettboom wrote: > I have tagged and created a tarball for 1.2.0rc1. The githash is > bda6dd9feab8. The tarball is on the github download page here: > > https://github.com/matplotlib/matplotlib/downloads > > I have created a new branch, v1.2.x, for continuing 1.2.x development. > The feature freeze on master is now lifted and big experimental changes > can be merged into master. Any bugfixes that need to go into 1.2.x > should be merged into both places. Please mark any PRs for the 1.2.x > branch with the 1.2.x milestone so we can verify that things are merged > in both places. > > For those creating the Windows and Macintosh builds, let's try using the > github download page rather than the one at Sourceforge this time. It > is a lot simpler. > > For those creating distro packages, now is a good time to let us know > what can be done to make the inclusion of matplotlib 1.2.0 as smooth as > possible. > > Once the binaries are available, I will make an announcement to > matplotlib-users. > > Mike > > Can we hold the Windows binaries until rc2? Setup.py corrupts the pytz package, leading to stack-overflows on Python 3 and other problems on Python 2. Christoph |
|
From: Thomas K. <th...@kl...> - 2012-09-12 16:39:47
|
On 12 September 2012 15:44, Michael Droettboom <md...@st...> wrote: > For those creating distro packages, now is a good time to let us know what > can be done to make the inclusion of matplotlib 1.2.0 as smooth as possible. I think I've mentioned before, but whoever does the Debian packages is welcome to use code from my bzr branch here: https://code.launchpad.net/~takluyver/matplotlib/debian-daily It's successfully building packages from master, including Python 3 packages, using the Launchpad recipe system: https://code.launchpad.net/~takluyver/+recipe/matplotlib-daily Thanks, Thomas |
|
From: Michael D. <md...@st...> - 2012-09-12 14:45:04
|
I have tagged and created a tarball for 1.2.0rc1. The githash is bda6dd9feab8. The tarball is on the github download page here: https://github.com/matplotlib/matplotlib/downloads I have created a new branch, v1.2.x, for continuing 1.2.x development. The feature freeze on master is now lifted and big experimental changes can be merged into master. Any bugfixes that need to go into 1.2.x should be merged into both places. Please mark any PRs for the 1.2.x branch with the 1.2.x milestone so we can verify that things are merged in both places. For those creating the Windows and Macintosh builds, let's try using the github download page rather than the one at Sourceforge this time. It is a lot simpler. For those creating distro packages, now is a good time to let us know what can be done to make the inclusion of matplotlib 1.2.0 as smooth as possible. Once the binaries are available, I will make an announcement to matplotlib-users. Mike |