You can subscribe to this list here.
2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(3) |
Jun
|
Jul
|
Aug
(12) |
Sep
(12) |
Oct
(56) |
Nov
(65) |
Dec
(37) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2004 |
Jan
(59) |
Feb
(78) |
Mar
(153) |
Apr
(205) |
May
(184) |
Jun
(123) |
Jul
(171) |
Aug
(156) |
Sep
(190) |
Oct
(120) |
Nov
(154) |
Dec
(223) |
2005 |
Jan
(184) |
Feb
(267) |
Mar
(214) |
Apr
(286) |
May
(320) |
Jun
(299) |
Jul
(348) |
Aug
(283) |
Sep
(355) |
Oct
(293) |
Nov
(232) |
Dec
(203) |
2006 |
Jan
(352) |
Feb
(358) |
Mar
(403) |
Apr
(313) |
May
(165) |
Jun
(281) |
Jul
(316) |
Aug
(228) |
Sep
(279) |
Oct
(243) |
Nov
(315) |
Dec
(345) |
2007 |
Jan
(260) |
Feb
(323) |
Mar
(340) |
Apr
(319) |
May
(290) |
Jun
(296) |
Jul
(221) |
Aug
(292) |
Sep
(242) |
Oct
(248) |
Nov
(242) |
Dec
(332) |
2008 |
Jan
(312) |
Feb
(359) |
Mar
(454) |
Apr
(287) |
May
(340) |
Jun
(450) |
Jul
(403) |
Aug
(324) |
Sep
(349) |
Oct
(385) |
Nov
(363) |
Dec
(437) |
2009 |
Jan
(500) |
Feb
(301) |
Mar
(409) |
Apr
(486) |
May
(545) |
Jun
(391) |
Jul
(518) |
Aug
(497) |
Sep
(492) |
Oct
(429) |
Nov
(357) |
Dec
(310) |
2010 |
Jan
(371) |
Feb
(657) |
Mar
(519) |
Apr
(432) |
May
(312) |
Jun
(416) |
Jul
(477) |
Aug
(386) |
Sep
(419) |
Oct
(435) |
Nov
(320) |
Dec
(202) |
2011 |
Jan
(321) |
Feb
(413) |
Mar
(299) |
Apr
(215) |
May
(284) |
Jun
(203) |
Jul
(207) |
Aug
(314) |
Sep
(321) |
Oct
(259) |
Nov
(347) |
Dec
(209) |
2012 |
Jan
(322) |
Feb
(414) |
Mar
(377) |
Apr
(179) |
May
(173) |
Jun
(234) |
Jul
(295) |
Aug
(239) |
Sep
(276) |
Oct
(355) |
Nov
(144) |
Dec
(108) |
2013 |
Jan
(170) |
Feb
(89) |
Mar
(204) |
Apr
(133) |
May
(142) |
Jun
(89) |
Jul
(160) |
Aug
(180) |
Sep
(69) |
Oct
(136) |
Nov
(83) |
Dec
(32) |
2014 |
Jan
(71) |
Feb
(90) |
Mar
(161) |
Apr
(117) |
May
(78) |
Jun
(94) |
Jul
(60) |
Aug
(83) |
Sep
(102) |
Oct
(132) |
Nov
(154) |
Dec
(96) |
2015 |
Jan
(45) |
Feb
(138) |
Mar
(176) |
Apr
(132) |
May
(119) |
Jun
(124) |
Jul
(77) |
Aug
(31) |
Sep
(34) |
Oct
(22) |
Nov
(23) |
Dec
(9) |
2016 |
Jan
(26) |
Feb
(17) |
Mar
(10) |
Apr
(8) |
May
(4) |
Jun
(8) |
Jul
(6) |
Aug
(5) |
Sep
(9) |
Oct
(4) |
Nov
|
Dec
|
2017 |
Jan
(5) |
Feb
(7) |
Mar
(1) |
Apr
(5) |
May
|
Jun
(3) |
Jul
(6) |
Aug
(1) |
Sep
|
Oct
(2) |
Nov
(1) |
Dec
|
2018 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2025 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Chris <rea...@po...> - 2004-10-01 21:03:42
|
Hi, I cannot build matplotlib-0.63.4 on gentoo linux. The error I get when running python setup.py build is: running build_ext building 'matplotlib._na_transforms' extension creating build/temp.linux-i686-2.3 creating build/temp.linux-i686-2.3/src creating build/temp.linux-i686-2.3/CXX gcc -fno-strict-aliasing -DNDEBUG -fPIC -Isrc -I. -I/usr/include/python2.3 -c CXX/IndirectPythonInterface.cxx -o build/temp.linux-i686-2.3/CXX/IndirectPythonInterface.o -DNUMARRAY=1 gcc -fno-strict-aliasing -DNDEBUG -fPIC -Isrc -I. -I/usr/include/python2.3 -c CXX/cxxsupport.cxx -o build/temp.linux-i686-2.3/CXX/cxxsupport.o -DNUMARRAY=1 In file included from CXX/cxxsupport.cxx:6: ./CXX/Objects.hxx: In constructor `Py::MapBase<T>::const_iterator::const_iterator(const Py::MapBase<T>*, Py::List, Py::SeqBase<Py::Object>::iterator)': ./CXX/Objects.hxx:2271: error: `s' undeclared (first use this function) ./CXX/Objects.hxx:2271: error: (Each undeclared identifier is reported only once for each function it appears in.) error: command 'gcc' failed with exit status 1 I have python 2.3.3, GCC 3.4.2, Numeric 23.3, numarray 1.0, pygtk-2.3.97 (I ungraded from pygtk-2.2.0 but that did not help), and wxpython-2.4.2.4 I hope that is enough information - do I have the wrong versions - or am I missing something - I had no trouble building matplotlib-0.62.x Cheers Chris |
From: <fcc...@fi...> - 2004-10-01 17:06:31
|
Hi, look at this: >>> from RandomArray import * >>> normal(2,2,10) array([ 2., 2., 2., 2., 2., 2., 2., 2., 2., 2.]) This is Numeric 23.1 compiled on my AMD64!!! I ran the same tests on a 32bit P4 and it ran fine. Has anyone else seen this before? For those that didn't understand, the normal function as called above, is supposed to give me ten samples form a normal distribution with mean = 2 and standard deviation = 2 luckily: >>> from numarray.random_array import * >>> normal(2,2,10) array([-0.04525638, 4.31467819, -0.17468357, 5.29377031, 0.84202135, 5.29593539, 4.69651532, 1.61354655, 1.10839236, 1.7743317 ]) If anybody still needed a reason for switching to numarray, there you go! I anybody here subscribes the numeric or numarray mailing lists (i.e. if they even exist) could you please forward this message to them? Flavio |
From: Matt N. <new...@ca...> - 2004-10-01 16:16:13
|
On Fri, 1 Oct 2004, Dominique Orban wrote: > I just downloaded the latest matplotlib (0.63.4) for Windows XP. I got > rid of my font cache to make sure they would be re-generated. I have two > questions/issues: > > 1) The font cache was not re-created, for some reason. > > 2) The spacing in math text does not seem to be rendered. I may be doing > something wrong. I have tried this in both the TkAgg and GTKAgg > backends. If i modify the example script mathtext_demo.py so the line > > title(r'$\Delta_i^j \hspace{0.4} \rm{versus} \hspace{0.4} > \Delta_{i+1}^j$', fontsize=20) > > becomes > > title(r'$\Delta_i^j \hspace{0.4} \rm{versus some} \hspace{0.4} > \Delta_{i+1}^j$', fontsize=20) > > the space between 'versus' and 'some' is not rendered on my machine. That's the normal behavior of TeX math-mode. I believe you want: \rm{versus \ some} --Matt |
From: Dominique O. <Dom...@po...> - 2004-10-01 16:06:26
|
I just downloaded the latest matplotlib (0.63.4) for Windows XP. I got rid of my font cache to make sure they would be re-generated. I have two questions/issues: 1) The font cache was not re-created, for some reason. 2) The spacing in math text does not seem to be rendered. I may be doing something wrong. I have tried this in both the TkAgg and GTKAgg backends. If i modify the example script mathtext_demo.py so the line title(r'$\Delta_i^j \hspace{0.4} \rm{versus} \hspace{0.4} \Delta_{i+1}^j$', fontsize=20) becomes title(r'$\Delta_i^j \hspace{0.4} \rm{versus some} \hspace{0.4} \Delta_{i+1}^j$', fontsize=20) the space between 'versus' and 'some' is not rendered on my machine. If you have any idea why that is, i'd be very grateful. Thanks, Dominique |
From: Steve C. <ste...@ya...> - 2004-10-01 02:20:28
|
> Hello! > > I have tried using matplotlib with pygtk 2.2 and everything worked fine. > But when I try to compile matplotlib (0.62.4) with the newest version of > pygtk, pygtk-2.3.96, I get the error included below. Since this pygtk > version is still in development, this might as well be a bug in pygtk. > > Maybe you can help me solve my problem, > > Niklas. I've recently installed the latest version of pygtk which is now 2.3.97 and matplotlib 0.63.0 and they did not give any install problems. I would recommend remove the directory 'python2.x/site-packages/matplotlib' remove the directory 'build' of your matplotlib install tree install pygtk 2.3.97 install matplotlib 0.63 Regards, Steve |
From: Curtis C. <cu...@hi...> - 2004-09-30 20:50:39
|
> So does the colorbar bug persist? > It appears to have been fixed! The colorbar labeling automatically determines the appropriate number of digits (or if scientific notation is necessary) for the text labels on the colorbar. You might want to activate the tickfmt optional parameter that is still present in the source code, as this gives the user direct control over the number of digits displayed, but at least the labels can be distinguished in the current version of the library. Thanks! Curtis |
From: John H. <jdh...@ac...> - 2004-09-30 18:01:00
|
Fernando Perez pointed out that there was a problem with the src distribution of matplotlib-0.63 and python2.2. I fixed these, and uploaded matplotlib-0.63.4.tar.gz to the sourceforge site. Should work for python2.2, but w/o date or mathtext support. JDH |
From: John H. <jdh...@ac...> - 2004-09-30 17:25:27
|
>>>>> "Curtis" == Curtis Cooper <cu...@hi...> writes: Curtis> This worked. I didn't realize I had to delete the Curtis> site-packages/matplotlib before installing over an old Curtis> version. You don't normally, but this is usually my first line of defense when something fails in one place that isn't failing in another. So does the colorbar bug persist? JDH |
From: Curtis C. <cu...@hi...> - 2004-09-30 17:08:53
|
> Try rm -rf site-packages/matplotlib and the 'build' dir of your > matplotlib install tree, and reinstall. This worked. I didn't realize I had to delete the site-packages/matplotlib before installing over an old version. |
From: david P. <dav...@kc...> - 2004-09-30 15:22:14
|
John Thank you for pointing me to the examples. It works for me too. Sorry to raise false alarm. Regards David -----Original Message----- From: John Hunter [mailto:jdh...@ac...] Sent: 30 September 2004 14:44 To: david Powell Cc: mat...@li... Subject: Re: [Matplotlib-users] mathtext >>>>> "david" == david Powell <dav...@kc...> writes: david> Thanks for previous help. Using 0.63.2 I now cannot render david> TEX symbols. david> Has anyone else done this under Windows? david> I appear to have the right Bakoma fonts in david> D:\Python23\share\matplotlib. david> I tried creating the environment variable TTFPATH at the david> python prompt to point to this directory but no luck. Works fine for me on windows XP. Can you run the mathtext_demo.py at http://matplotlib.sf.net/examples/mathtext_demo.py ? What backend are you using - tkagg is the default and should be set in D:\Python23\share\.matplotlibrc according to the info you provided above. JDH |
From: Humufr <hu...@ya...> - 2004-09-30 15:10:14
|
Hi John, you're solution is working for the first problem but not for the second, the little tick are not changing (cf figure and script). The size of the tick lines are not change so they are not very visible if you change the size of the lines. Nicolas script with the problem (but all errobar script will have the same I think): #!/usr/bin/env python # -*- coding: utf-8 -*- import sys import numarray from matplotlib.matlab import * from math import * sigma_final = numarray.array([74.8,172.27,206.,133.4,309.3,196.6,259.8,137.1,183.4 ]) sigma_error = numarray.array([49.6,69.54,11.4,91.2,45.7,15.9,37.3,50.,10.2]) sigma_emi = numarray.array([80.,65.,130.,55.,108.,250.,60.,50.,50.]) ligne = numarray.array([0,400]) fonts = { 'color' : 'k', 'fontname' : 'Courier', 'fontweight' : 'bold', 'fontsize' : 'xx-large' } figure(num = 1, figsize=(8, 8), dpi=100, facecolor='w', edgecolor='k') xlabel('$\sigma 1$',fonts) ylabel('$\sigma 2$',fonts) errlines = errorbar(sigma_emi,sigma_final,sigma_error, fmt='o',capsize=5) set(errlines, linewidth=3) plot(sigma_emi,sigma_final,'s', linewidth=2) plot(ligne,ligne, linewidth=2) xticklabels = get(gca(), 'xticklabels') set(xticklabels, 'fontsize', 'medium') yticklabels = get(gca(), 'yticklabels') set(yticklabels, 'fontsize', 'medium') axis([0,360,0,360]) show() John Hunter wrote: >>>>>>"Humufr" == Humufr <hu...@ya...> writes: >>>>>> >>>>>> > > Humufr> Hello, I found a problem with the > Humufr> function errorbar. I'm trying to change the width of the > Humufr> errorbar. The only way to do this seems to pass by the > Humufr> file .matplotlibrc and the default line width (it's not > Humufr> very useful I think and an option linewidth will be > Humufr> welcome in the errorbar function). The second problem is > Humufr> for the caps who are not change even with the global > Humufr> change (see figure in attachement). > > >You can set the linewidth of the errorbar lines and caps by using the >return value from errorbar > > lines, errlines = errorbar(x,y,err) > set(errlines, linewidth=4) > >Let me know if this helps. If not, please post a script that exposes >the problem. > >JDH > > > > |
From: Humufr <hu...@ya...> - 2004-09-30 14:55:06
|
Hi John, this was the solution thanks. I was deleting the older .fonts.cache. I didn't notice the change, I'm apoligizing for the disturbance. Thanks again, Nicolas >Are you sure that you have Courier and Arial on your system and are >they in your TTFPATH? > >If you are sure on both counts, it may help to remove your font cache >(typically ~/.ttffont.cache on linux like systems) and let matplotlib >regenerate it's cache. > >Those are my only ideas so far, let me know. > >JDH > > > |
From: John H. <jdh...@ac...> - 2004-09-30 14:34:00
|
>>>>> "Jean-Michel" == Jean-Michel Philippe <jea...@ir...> writes: Jean-Michel> It seems that show() hangs if no figure has been Jean-Michel> created before calling (under matplotlib 0.62.4). Am Jean-Michel> I wrong or is it an unexpected use of show() ? show should be the last line of your script. It is expected to hang. It starts the GUI mainloop after which all processing is done in the GUI event handling (unless you are using threading). See http://matplotlib.sf.net/faq.html#SHOW JDH |
From: John H. <jdh...@ac...> - 2004-09-30 14:32:27
|
>>>>> "david" == david Powell <dav...@kc...> writes: david> Thanks for previous help. Using 0.63.2 I now cannot render david> TEX symbols. david> Has anyone else done this under Windows? david> I appear to have the right Bakoma fonts in david> D:\Python23\share\matplotlib. david> I tried creating the environment variable TTFPATH at the david> python prompt to point to this directory but no luck. Works fine for me on windows XP. Can you run the mathtext_demo.py at http://matplotlib.sf.net/examples/mathtext_demo.py ? What backend are you using - tkagg is the default and should be set in D:\Python23\share\.matplotlibrc according to the info you provided above. JDH |
From: John H. <jdh...@ac...> - 2004-09-30 14:31:04
|
>>>>> "Curtis" == Curtis Cooper <cu...@hi...> writes: >> Could you test this with 0.63 and if the problem persists post >> a minimal script that exposes the bug? Curtis> In matplotlib-0.63.0, I can't even get the examples Curtis> pcolor_demo.py and pcolor_demo2.py to work properly. My Curtis> code mimics these examples closely. Once they are working Curtis> again, I will send you an example of the colorbar tick Curtis> format issue. Strange. pcolor_demo.py and pcolor_demo2.py work fine for me on linux and win32. Try rm -rf site-packages/matplotlib and the 'build' dir of your matplotlib install tree, and reinstall. What, by the way, does it mean to "not work properly". Is this a crash? Note an image interpolation bug was fixed in 0.63.0 which will cause the axes limits to be a little different for imshow calls than they were before. Earlier versions of matplotlib set the viewlim to hide the edge artifacts, which no longer exist. JDH |
From: Stephen W. <ste...@cs...> - 2004-09-30 13:22:47
|
On Tue, 2004-09-28 at 18:52, John Hunter wrote: > Once you have > your n, bins from your custom function, you can call bar, just as > hist does. Ie it's so easy to plot a histogram using bar that you > may not need to bother with altering the matplotlib.matlab hist. I personally vote for this option. I had a similar need just a couple of days ago, namely creating a summed histogram from a number of repeated simulations, and I just did the sums myself and called bar. It is probably best to keep matplotlib.matlab hist clean and simple. Steve Walton |
From: david P. <dav...@kc...> - 2004-09-30 11:36:59
|
Thanks for previous help. Using 0.63.2 I now cannot render TEX symbols. Has anyone else done this under Windows? I appear to have the right Bakoma fonts in D:\Python23\share\matplotlib. I tried creating the environment variable TTFPATH at the python prompt to point to this directory but no luck. David |
From: Curtis C. <cu...@hi...> - 2004-09-30 10:54:56
|
> Could you test this with 0.63 and if the problem persists post a > minimal script that exposes the bug? In matplotlib-0.63.0, I can't even get the examples pcolor_demo.py and pcolor_demo2.py to work properly. My code mimics these examples closely. Once they are working again, I will send you an example of the colorbar tick format issue. Cheers, Curtis |
From: Jean-Michel P. <jea...@ir...> - 2004-09-30 08:14:29
|
jdh...@ac... wrote: > In truth, the latest release of matplotlib sets a flag on show to > prevent repeated calls from doing any real damage. > > But for classroom use, I suggest you just put "interactive : True" in > your rc file and then you have no need for show. Is there a downside > to this approach? > > JDH It seems that show() hangs if no figure has been created before calling (under matplotlib 0.62.4). Am I wrong or is it an unexpected use of show() ? JM. Philippe |
From: Peter G. <pgr...@ge...> - 2004-09-30 03:50:36
|
John Hunter wrote: >>>>>>"Peter" == Peter Groszkowski <pgr...@ge...> writes: >>>>>> > Peter> doing this would be to incorporate it into the plot() > Peter> command. Perhaps adding an option 'steps' (following > Peter> gnuplot's convention could have steps equal 'histeps', > Peter> 'fsteps' or just 'steps' - see link above.. None could mean > Peter> regular plot() behavior). I would say this would be the > Peter> most elegant option, but probably would call for John (or > Peter> someone else from the core developers) to make the > Peter> changes. Alternatively we could use above and wrap it in a > Peter> plot_step() function. > > Peter> Any interest in this? If so which way do we want to go? > >It might be easiest to make this a line style. Then you could use the >builtin kwarg linestyle > > plot(x, y, linestyle='steps') > >It shouldn't be too hard to modify lines.py to support this. If you >want to take a stab at it, I'd be happy to include it. > Alrgith.. .this is my version of it.. just modifies lines.py (i'm using 0.60.2 by the way).. : def _draw_steps(self, renderer, gc, xt, yt): siz=len(xt) if siz<2: return xt2=ones((2*siz,), xt.typecode()) xt2[0:-1:2], xt2[1:-1:2], xt2[-1]=xt, xt[1:], xt[-1] yt2=ones((2*siz,), yt.typecode()) yt2[0:-1:2], yt2[1::2]=yt, yt gc.set_linestyle('solid') gc.set_capstyle('projecting') renderer.draw_lines(gc, xt2, yt2) also changed: class Line2D(Artist): _lineStyles = { '-' : '_draw_solid', '--' : '_draw_dashed', '-.' : '_draw_dash_dot', ':' : '_draw_dotted', 'steps': '_draw_steps', 'None' : '_draw_nothing'} and: lineStyles = {'-':1, '--':1, '-.':1, ':':1, 'steps':1, 'None':1} maybe a more memory friendly way to do this would be to loop through the arrays xt,yt and create extra points on the fly; then draw lines separately, but from my testing this current way seems (by far) the fastest.. im got lots of RAM and am in 'need for speed', so this works for me.. > The nice thing >about making it a line style is that the changes required would all be >contained to the lines.py file which is simple and clear. If you >change how plot processes its arguments, it's easy to foul things up. > > yeah.. now that i know how things work a little better - i agree.. >The only potential problem I see is this would prevent you from, for >example, having a dashed stepped line, since dash is itself a line >style. But who needs a dashed stepped line, for heaven's sake? > > could always add.. 'steps--' if needed.. althought that's a little ugly!.. |
From: Gary <pa...@in...> - 2004-09-29 21:50:11
|
John Hunter wrote: [...] > John> Sorry for the troubles > >Ditto > >JDH > > You can't be serious. Think about it: where else can we talk to the developer of the software, get our questions answered almost instantly, and our requests for features satisfied in a matter of weeks if not days or hours? You have nothing to be sorry about. -gary |
From: John H. <jdh...@ac...> - 2004-09-29 21:20:47
|
>>>>> "Humufr" == Humufr <hu...@ya...> writes: Humufr> Hello, I found a problem with the Humufr> function errorbar. I'm trying to change the width of the Humufr> errorbar. The only way to do this seems to pass by the Humufr> file .matplotlibrc and the default line width (it's not Humufr> very useful I think and an option linewidth will be Humufr> welcome in the errorbar function). The second problem is Humufr> for the caps who are not change even with the global Humufr> change (see figure in attachement). You can set the linewidth of the errorbar lines and caps by using the return value from errorbar lines, errlines = errorbar(x,y,err) set(errlines, linewidth=4) Let me know if this helps. If not, please post a script that exposes the problem. JDH |
From: John H. <jdh...@ac...> - 2004-09-29 21:17:55
|
>>>>> "Humufr" == Humufr <hu...@ya...> writes: Humufr> the different fonts available. I obtain: Humufr> ['Lucida Grande', 'Verdana', 'Geneva', 'Lucida', Humufr> 'Bitstream Vera Sans', 'Arial', 'Helvetica', 'sans-serif'] Humufr> but if I'm trying to use the font Arial and italic in the Humufr> script that give me this message: Could not match Humufr> sans-serif, italic, normal. Returning Humufr> /usr/share/fonts/truetype/ttf-bitstream-vera/Vera.ttf Humufr> It's seems that the change introduce in the script is not Humufr> use and that matplotlib are using only Vera fonts with no Humufr> style. Note that this list does not mean that these fonts are available on your system. They are simply the fonts that matplotlib will look for if you specify sans-serif. Humufr> fonts = { 'color' : 'k', 'fontname' : 'Courier', Humufr> 'fontweight' : 'bold', 'fontstyle' : 'italic', 'fontsize' Humufr> : 'xx-large' Humufr> } Humufr> ylabel('toto',fonts) Humufr> give me exactly the same things than: Humufr> fonts = { 'color' : 'k', 'fontname' : 'Arial, 'fontweight' Humufr> : 'bold', 'fontstyle' : 'italic', 'fontsize' : 'xx-large' Humufr> } Are you sure that you have Courier and Arial on your system and are they in your TTFPATH? If you are sure on both counts, it may help to remove your font cache (typically ~/.ttffont.cache on linux like systems) and let matplotlib regenerate it's cache. Those are my only ideas so far, let me know. JDH |
From: Matt N. <new...@ca...> - 2004-09-29 17:11:51
|
> Arrgg. The matplotlib-0.63.1.win32-py2.3.exe file must have gotten > clipped in transfer; it's broken. I just uploaded > matplotlib-0.63.2.win32-py2.3.exe; this *will work*. These bug fix > numbers are ticking like mad. Yep, this works for me... Thanks! --Matt |
From: John H. <jdh...@ac...> - 2004-09-29 16:52:07
|
John> This was a bug in the creation of the windows installer, John> which should have included these packages. Grab John> matplotlib-0.63.1.win32-py2.3.exe from sf, which was just John> updated minutes ago after someone alerted me to this problem John> off-list. Arrgg. The matplotlib-0.63.1.win32-py2.3.exe file must have gotten clipped in transfer; it's broken. I just uploaded matplotlib-0.63.2.win32-py2.3.exe; this *will work*. These bug fix numbers are ticking like mad. John> Sorry for the troubles Ditto JDH |