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
|
2
|
|
3
|
4
(2) |
5
(8) |
6
(10) |
7
(6) |
8
(4) |
9
(4) |
|
10
(2) |
11
(1) |
12
(3) |
13
(4) |
14
(4) |
15
|
16
|
|
17
|
18
|
19
(4) |
20
(6) |
21
(5) |
22
(2) |
23
|
|
24
(2) |
25
(3) |
26
(2) |
27
(1) |
28
(4) |
29
|
30
|
Yup, looks like the matplotlib-0.87.5.win32-py2.4.exe binary's been fixed. Thanks! Martin Boyd Waters wrote: > Try downloading again? > > I have not tried the windows binary, but a source tarball from this > morning was strange. > > I pulled a 0.87.5 tarball this morning that had lots of permissions > problems, an empty __init__.py, weird line terminators... permissions > looked like it had been filtered through a DOS filesystem. That tarball > had an MD5 checksum of 6cc874f1b4adf95c7aac5c39a38b5517. > > I tried again this afternoon, I got a cleaner source tarball, MD5 > af3015ceae28ab385dbe9f30c6d2f83e. > > - boyd >
Thanks alot, everything seems to be ok now! (with numpy 1.0b5) -sven Charlie Moad schrieb: > Sorry all for the error. I just uploaded "working" (at least for me) > versions to sourceforge again. For those who are sicking of playing > with mirrors here is a direct download. Don't expect this link to be > good for a long time though. > > http://euclid.uits.iupui.edu/mplfiles/ > > - Charlie > > On 9/6/06, Charlie Moad <cw...@gm...> wrote: >> The source error must of propagated to those builds. I will post new >> ones shortly. >> >> On 9/6/06, Sven Schreiber <sve...@gm...> wrote: >> > Well the thread on the devel list that I referred to explicitly has the >> > win32 exe in its title ("Missing __init__.py in >> > matplotlib-0.87.5.win32-py2.4.exe ?") . The starting post there pretty >> > much says it all. >> > >> > There's also a recent post on the numpy list that sounds like it's >> maybe >> > the same problem (quote): >> > """ >> > Is there a compatible matplotlib as well? I was o.k. with mpl from >> > enthought until I switched numerix to numpy. That made mpl unhappy. >> > I downloaded 0.87.5 but I broke something in the process because now >> > even switching back to Numeric doesn't make mpl happy. >> > """ >> > >> > Thanks, >> > Sven >> > >> > Charlie Moad schrieb: >> > > That error was relating to the source release. Can you please post >> > > your error for the binary? >> > > >> > > On 9/6/06, Sven Schreiber <sve...@gm...> wrote: >> > >> Charlie Moad schrieb: >> > >> > Minor rev bump for numpy 1.0b5 compatibility. This release should >> > >> > remain compatible with future 1.0 releases of numpy. >> > >> > >> > >> >> > >> I keep running into the ImportError problem described on the >> devel list, >> > >> with the win32 2.4 binary (exe). Is that still just a case of >> waiting >> > >> for the mirrors to update, or is there a deeper problem? Are there >> > >> alternative download links? How to tell whether it's the "right" >> binary, >> > >> since version numbers are the same? >> > >> >> > >> Thanks for your help, >> > >> Sven >> > >> >> > > >> > >> > >> >
Sorry all for the error. I just uploaded "working" (at least for me) versions to sourceforge again. For those who are sicking of playing with mirrors here is a direct download. Don't expect this link to be good for a long time though. http://euclid.uits.iupui.edu/mplfiles/ - Charlie On 9/6/06, Charlie Moad <cw...@gm...> wrote: > The source error must of propagated to those builds. I will post new > ones shortly. > > On 9/6/06, Sven Schreiber <sve...@gm...> wrote: > > Well the thread on the devel list that I referred to explicitly has the > > win32 exe in its title ("Missing __init__.py in > > matplotlib-0.87.5.win32-py2.4.exe ?") . The starting post there pretty > > much says it all. > > > > There's also a recent post on the numpy list that sounds like it's maybe > > the same problem (quote): > > """ > > Is there a compatible matplotlib as well? I was o.k. with mpl from > > enthought until I switched numerix to numpy. That made mpl unhappy. > > I downloaded 0.87.5 but I broke something in the process because now > > even switching back to Numeric doesn't make mpl happy. > > """ > > > > Thanks, > > Sven > > > > Charlie Moad schrieb: > > > That error was relating to the source release. Can you please post > > > your error for the binary? > > > > > > On 9/6/06, Sven Schreiber <sve...@gm...> wrote: > > >> Charlie Moad schrieb: > > >> > Minor rev bump for numpy 1.0b5 compatibility. This release should > > >> > remain compatible with future 1.0 releases of numpy. > > >> > > > >> > > >> I keep running into the ImportError problem described on the devel list, > > >> with the win32 2.4 binary (exe). Is that still just a case of waiting > > >> for the mirrors to update, or is there a deeper problem? Are there > > >> alternative download links? How to tell whether it's the "right" binary, > > >> since version numbers are the same? > > >> > > >> Thanks for your help, > > >> Sven > > >> > > > > > > > >
The source error must of propagated to those builds. I will post new
ones shortly.
On 9/6/06, Sven Schreiber <sve...@gm...> wrote:
> Well the thread on the devel list that I referred to explicitly has the
> win32 exe in its title ("Missing __init__.py in
> matplotlib-0.87.5.win32-py2.4.exe ?") . The starting post there pretty
> much says it all.
>
> There's also a recent post on the numpy list that sounds like it's maybe
> the same problem (quote):
> """
> Is there a compatible matplotlib as well? I was o.k. with mpl from
> enthought until I switched numerix to numpy. That made mpl unhappy.
> I downloaded 0.87.5 but I broke something in the process because now
> even switching back to Numeric doesn't make mpl happy.
> """
>
> Thanks,
> Sven
>
> Charlie Moad schrieb:
> > That error was relating to the source release. Can you please post
> > your error for the binary?
> >
> > On 9/6/06, Sven Schreiber <sve...@gm...> wrote:
> >> Charlie Moad schrieb:
> >> > Minor rev bump for numpy 1.0b5 compatibility. This release should
> >> > remain compatible with future 1.0 releases of numpy.
> >> >
> >>
> >> I keep running into the ImportError problem described on the devel list,
> >> with the win32 2.4 binary (exe). Is that still just a case of waiting
> >> for the mirrors to update, or is there a deeper problem? Are there
> >> alternative download links? How to tell whether it's the "right" binary,
> >> since version numbers are the same?
> >>
> >> Thanks for your help,
> >> Sven
> >>
> >
>
>
Well the thread on the devel list that I referred to explicitly has the
win32 exe in its title ("Missing __init__.py in
matplotlib-0.87.5.win32-py2.4.exe ?") . The starting post there pretty
much says it all.
There's also a recent post on the numpy list that sounds like it's maybe
the same problem (quote):
"""
Is there a compatible matplotlib as well? I was o.k. with mpl from
enthought until I switched numerix to numpy. That made mpl unhappy.
I downloaded 0.87.5 but I broke something in the process because now
even switching back to Numeric doesn't make mpl happy.
"""
Thanks,
Sven
Charlie Moad schrieb:
> That error was relating to the source release. Can you please post
> your error for the binary?
>
> On 9/6/06, Sven Schreiber <sve...@gm...> wrote:
>> Charlie Moad schrieb:
>> > Minor rev bump for numpy 1.0b5 compatibility. This release should
>> > remain compatible with future 1.0 releases of numpy.
>> >
>>
>> I keep running into the ImportError problem described on the devel list,
>> with the win32 2.4 binary (exe). Is that still just a case of waiting
>> for the mirrors to update, or is there a deeper problem? Are there
>> alternative download links? How to tell whether it's the "right" binary,
>> since version numbers are the same?
>>
>> Thanks for your help,
>> Sven
>>
>
That error was relating to the source release. Can you please post your error for the binary? On 9/6/06, Sven Schreiber <sve...@gm...> wrote: > Charlie Moad schrieb: > > Minor rev bump for numpy 1.0b5 compatibility. This release should > > remain compatible with future 1.0 releases of numpy. > > > > I keep running into the ImportError problem described on the devel list, > with the win32 2.4 binary (exe). Is that still just a case of waiting > for the mirrors to update, or is there a deeper problem? Are there > alternative download links? How to tell whether it's the "right" binary, > since version numbers are the same? > > Thanks for your help, > Sven >
Charlie Moad schrieb: > Minor rev bump for numpy 1.0b5 compatibility. This release should > remain compatible with future 1.0 releases of numpy. > I keep running into the ImportError problem described on the devel list, with the win32 2.4 binary (exe). Is that still just a case of waiting for the mirrors to update, or is there a deeper problem? Are there alternative download links? How to tell whether it's the "right" binary, since version numbers are the same? Thanks for your help, Sven
On 9/5/06, Boyd Waters <bw...@nr...> wrote: > Try downloading again? > > I have not tried the windows binary, but a source tarball from this > morning was strange. > > I pulled a 0.87.5 tarball this morning that had lots of permissions > problems, an empty __init__.py, weird line terminators... permissions > looked like it had been filtered through a DOS filesystem. That > tarball had an MD5 checksum of 6cc874f1b4adf95c7aac5c39a38b5517. > > I tried again this afternoon, I got a cleaner source tarball, MD5 > af3015ceae28ab385dbe9f30c6d2f83e. You caught me : ) . The first source had windows line feeds and linux choked on it. I removed it and put up a fresh copy after a few hours. Some of the mirrors may of taken a while to update. If you have problems please try downloading the source again. - Charlie
Try downloading again? I have not tried the windows binary, but a source tarball from this morning was strange. I pulled a 0.87.5 tarball this morning that had lots of permissions problems, an empty __init__.py, weird line terminators... permissions looked like it had been filtered through a DOS filesystem. That tarball had an MD5 checksum of 6cc874f1b4adf95c7aac5c39a38b5517. I tried again this afternoon, I got a cleaner source tarball, MD5 af3015ceae28ab385dbe9f30c6d2f83e. - boyd Boyd Waters Scientific Programmer National Radio Astronomy Observatory On Sep 5, 2006, at 8:13 PM, Martin Spacek wrote: > Not sure if I'm crazy, but it seems the __init__.py file is missing > from > my newly installed version 0.87.5. I installed from the > matplotlib-0.87.5.win32-py2.4.exe binary. I now get: > >>>> import matplotlib > Traceback (most recent call last): > File "<stdin>", line 1, in ? > ImportError: No module named matplotlib > > even though the folder's there in site-packages. Examining the binary > shows that indeed, the file is missing in the PLATLIB/matplotlib > folder, > yet it's there in the lib/matplotlib folder in the > matplotlib-0.87.5.tar.gz source file. > > I now also have a new folder 'matplotlib-0.87.5-py2.4.egg-info' in my > site-packages, as well as a file 'matplotlib-0.87.5-py2.4- > nspkg.pth' in > the same folder. > > Can this be fixed? > > Martin > > ---------------------------------------------------------------------- > --- > Using Tomcat but need to do more? Need to support web services, > security? > Get stuff done quickly with pre-integrated technology to make your > job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache > Geronimo > http://sel.as-us.falkag.net/sel? > cmd=lnk&kid=120709&bid=263057&dat=121642 > _______________________________________________ > Matplotlib-devel mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
Not sure if I'm crazy, but it seems the __init__.py file is missing from my newly installed version 0.87.5. I installed from the matplotlib-0.87.5.win32-py2.4.exe binary. I now get: >>> import matplotlib Traceback (most recent call last): File "<stdin>", line 1, in ? ImportError: No module named matplotlib even though the folder's there in site-packages. Examining the binary shows that indeed, the file is missing in the PLATLIB/matplotlib folder, yet it's there in the lib/matplotlib folder in the matplotlib-0.87.5.tar.gz source file. I now also have a new folder 'matplotlib-0.87.5-py2.4.egg-info' in my site-packages, as well as a file 'matplotlib-0.87.5-py2.4-nspkg.pth' in the same folder. Can this be fixed? Martin