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
(1) |
4
|
5
|
6
(1) |
7
(1) |
8
|
9
(4) |
10
(2) |
11
(1) |
12
(6) |
13
(1) |
14
(1) |
15
(3) |
16
(1) |
17
(8) |
18
(6) |
19
|
20
|
21
|
22
|
23
(5) |
24
|
25
(1) |
26
|
27
(4) |
28
|
29
|
30
(1) |
|
|
|
Just wanted to re-ping the list, but include John and Ben directly: can we get the appropriate commit tagged as v1.1.0 in the git repo? On Thu, Nov 3, 2011 at 2:21 PM, Paul Ivanov <piv...@gm...> wrote: > I added a note to the release docs about tagging the releases - right > now, there's no clear way inside git to know what ended up in v1.1.0 > final, without grabbing a tarball and poking around. I'm inlining the > relevant part of that commit here, so that John/Ben can tag the > release after the fact. > > --- > For each release candidate as well as for the final release version, > please `git tag` the commit you will use for packaging like so:: > > git tag -a v1.1.0rc1 > > The `-a` flag will allow you to write a message about the tag, and > affiliate your name with it. A reasonable tag message would be something > like ``v1.1.0 Release Candidate 1 (September 24, 2011)``. To tag a > release after the fact, just track down the commit hash, and:: > > git tag -a v1.0.1 a9f3f3a50745 > > Tags allow developers to quickly checkout different releases by name, > and also provides source download via zip and tarball on github. > --- best, -- Paul Ivanov 314 address only used for lists, off-list direct email at: http://pirsquared.org | GPG/PGP key id: 0x0F3E28F7
2011年10月22日 Eric Firing <ef...@ha...>: > moved from matplotlib-users: > > http://sourceforge.net/mailarchive/forum.php?thread_name=CAN06%3DCx2zgh8YrnF2WRaJ%3D0E8i3ROLdYW4VuurtqKrx3mdkeEg%40mail.gmail.com&forum_name=matplotlib-users OK > On 10/22/2011 09:31 AM, Friedrich Romstedt wrote: >> >> 2011年10月21日 Friedrich Romstedt<fri...@gm...>: >> <snippet> >> 3) Providing a dedicated Filter class, that can be fed to >> set_filter() instead of set_gray(). This I like best. >> </snippet> >> >> So the filter idea was Ben's idea. I still like idea (3) for the >> design best. I will check if it is possible to inject the filter code >> into the renderer framework, since all colour settings arguments >> somewhen flow into a call into the renderer. This is apparently a no-go. The backends are too tightly bound to the C extensions moduled, e.g. aggdraw. E.g. the image drawing method of the Agg backend is directly assigned in the fashion:: self.draw_image = self._renderer.draw_image So no, this will not work this way. >> Pro: No rcParams >> addition necessary, no modification of the peculiar colors.py >> ColorConverter framework necessary, just leaving those things >> untouched and hence no worries and headaches about them. So I'll touch it again. I will just check my refactor I did a year ago on ColorConverter, which was pretty decent, but well, it needs some check. I would first commit that to my repo, than people who are interested can test, and then we can go on testing the higher level functionality. I think the filters will, instead of signalling colors.colorConveter via rcParams that some conversion mode is turned on, signal that in the decorator function simply directly to colors.colorConverter. There are some open ends, though. >> No disabling >> of higher-level caching and at the same time negligible small impact >> if there is no filter active. Con: I don't know yet if it works. I >> vaguely remember there were some problems when I checked that >> possibility last time (with pixmaps or something like that). I think >> I will find out soon enough. :-) Apparently I found out the same thing a year ago. The methodology will be like this: The Artists can store a stack of filters, and also provide some easy-appetite-wetter .set_gray() method. When their draw method is decorated with a special decorator, say @filtered, then the filters will be activated upon entering and deactivated upon exit. The activation happens via putting the filters onto the filter stack in the ColorConverter instance. I'm pretty sure this will work, somehow at least. ;-) I've run into some strange Bus error compiling the latest matplotlib, I'll drop another email on the user list probably (since I'm acting here as a user, I just want to run the tests). Friedrich