matplotlib-users Mailing List for matplotlib (Page 6)

Hi Hans,
I just tried this out and found that setting "interactive" to "True" in
C:\python23\share\matplotlib\.matplotlibrc obviated the need to use the
show() command. The plot then comes up as soon as you issue the plot()
command. Multiple plotting-closing cycles worked fine in the same Idle
session.
Regards,
Todd
On Tue, 2005年01月11日 at 14:29, Hans Fangohr wrote:
> Dear all,
> 
> I tried to make matplotlib work with IDLE on Windows. I have settled for 
> the Enthough Python Edition and the latest matplotlib (both executables 
> can be found in www.soton.ac.uk/~fangohr/download/python).
> 
> I have prepared the exercises on linux and am now trying to run them in
> windows. This is where I realised that matplotlib doesn't work well with
> IDLE.
> 
> More particularly, it is known that the default backend TkAgg doesn't work
> with IDLE (see here http://matplotlib.sourceforge.net/backends.html#TkAgg)
> but it appears to work with "IDLE -n" (as it says on that web page).
> 
> The problem I experience is this:
> 
> -start idle
> -execute these commands:
> 
> import pylab
> pylab.plot(range(10))
> pylab.show()
> 
> This produces a figure window which seems to work fine.
> 
> At this point when closing the figure window, I can't get the IDLE
> prompt active again. (It seems that IDLE thinks the program and the figure
> process are still running, and is waiting for control to return.)
> 
> This, in itself, is maybe not suprising. However, the idle -n switch
> doesn't seem to solve the problem for me (see below).
> 
> The same problem is observed when I execute a program in the IDLE editor
> (by pressing F5).
> 
> Maybe this is the problem:
> 
> I have tried to tell IDLE to start with the "-n" by modifying the properties for the
> IDLE link in the start menu from
> 
> C:\Python23\pythonw.exe "C:\Python23\Lib\idlelib\idle.pyw"
> 
> to
> 
> C:\Python23\pythonw.exe "C:\Python23\Lib\idlelib\idle.pyw" "-n"
> 
> but this doesn't seem to solve the problem: I get exactly the same
> behaviour as described above. Am I doing the right thing?
> 
> Can anyone give me some advice?
> 
> Many thanks,
> 
> Hans
> 
> 
> P.S. Funnily enough, there are two Windows machines with a very similar 
> software setup, i.e. enthought python plus matplotlib, where the default 
> TkAgg interface seems to work happily togethe with IDLE. Unfortunately, 
> these are not the ones I am trying to get to work :-|
> 
> 
> 
> 
> 
> -------------------------------------------------
> Dr Hans Fangohr
> 
> Computational Engineering & Design Research Group
> School of Engineering Sciences
> University of Southampton
> Southampton, SO17 1BJ
> United Kingdom
> 
> Location: Building 25, Room 1027
> phone : +44 (0) 23 8059 8345
> fax : +44 (0) 23 8059 7082
> email : fa...@so...
> -------------------------------------------------
> 
> 
> 
> -------------------------------------------------------
> The SF.Net email is sponsored by: Beat the post-holiday blues
> Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
> It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
-- 

Dear all,
I tried to make matplotlib work with IDLE on Windows. I have settled for 
the Enthough Python Edition and the latest matplotlib (both executables 
can be found in www.soton.ac.uk/~fangohr/download/python).
I have prepared the exercises on linux and am now trying to run them in
windows. This is where I realised that matplotlib doesn't work well with
IDLE.
More particularly, it is known that the default backend TkAgg doesn't work
with IDLE (see here http://matplotlib.sourceforge.net/backends.html#TkAgg)
but it appears to work with "IDLE -n" (as it says on that web page).
The problem I experience is this:
-start idle
-execute these commands:
 import pylab
 pylab.plot(range(10))
 pylab.show()
This produces a figure window which seems to work fine.
At this point when closing the figure window, I can't get the IDLE
prompt active again. (It seems that IDLE thinks the program and the figure
process are still running, and is waiting for control to return.)
This, in itself, is maybe not suprising. However, the idle -n switch
doesn't seem to solve the problem for me (see below).
The same problem is observed when I execute a program in the IDLE editor
(by pressing F5).
Maybe this is the problem:
I have tried to tell IDLE to start with the "-n" by modifying the properties for the
IDLE link in the start menu from
C:\Python23\pythonw.exe "C:\Python23\Lib\idlelib\idle.pyw"
to
C:\Python23\pythonw.exe "C:\Python23\Lib\idlelib\idle.pyw" "-n"
but this doesn't seem to solve the problem: I get exactly the same
behaviour as described above. Am I doing the right thing?
Can anyone give me some advice?
Many thanks,
Hans
P.S. Funnily enough, there are two Windows machines with a very similar 
software setup, i.e. enthought python plus matplotlib, where the default 
TkAgg interface seems to work happily togethe with IDLE. Unfortunately, 
these are not the ones I am trying to get to work :-|
-------------------------------------------------
Dr Hans Fangohr
Computational Engineering & Design Research Group
School of Engineering Sciences
University of Southampton
Southampton, SO17 1BJ
United Kingdom
Location: Building 25, Room 1027
phone : +44 (0) 23 8059 8345
fax : +44 (0) 23 8059 7082
email : fa...@so...
-------------------------------------------------

Hi,
> thank you for your hints. If I understand you right,
> Matlibplot should be able to display the french characters and
> there is no need for \acute etc. 
Sorry for the confusion, that's not what I meant. I think that
the acute sign would have to be added to the list of symbols that
mathtext can handle. That would probably mean both special code
in mathtext.py and an entry in _mathtext_data.py. I'm not sure
what the right entry in the font table would be, as I don't
understand the entries in the latex_to_bakoma dictionary in
_mathtext_data.py at all.
--Matt

Eric Emsellem a écrit :
> Hi,
>
> 2 issues:
>
> 1/ just to remind you that I am still looking for a solution to the 
> previously
> mentioned bug in imshow (in terms of aspect='preserve').
>
> 2/ I have another problem with imshow:
>
> When I do for example:
>
> figure(1)
> axes([-0.1,0,0.8,0.8])
> myima = rand(50,50)
> imshow(myima)
>
> then it works and shows me the array with the axes partly outside the 
> window
> since the origin for the X axis is < 0
>
> However if I do:
>
> figure(1)
> axes([0,-0.1,0.8,0.8])
> myima = rand(50,50)
> imshow(myima)
>
> with this time the Y origin < 0:
>
> then I get a SEGMENTATION FAULT
>
> ??
> thanks for any help there...
>
> Eric
>
I reproduce this bug with GTK and TKagg.
With DEBUG = 1 I get this (may help):
axes([0,-0.1,0.8,0.8])
myima = rand(50,50)
In [5]: imshow(myima)
FigureCanvasGTKAgg.draw
Segmentation fault
Xavier

Dear Matt,
thank you for your hints. If I understand you right, Matlibplot should =
be able to display the french characters and there is no need for \acute =
etc. That's interesting and I would appreciate it. However e.g. =
title('Temp=E9rature') does not work properly. Instead of =E9 I see a =
rectangle on the screen. May be something is wrong with my installation?
Regards
Gerhard
-----Urspr=FCngliche Nachricht-----
Von: Matt Newville [mailto:new...@ca...]=20
Gesendet: Dienstag, 11. Januar 2005 18:03
An: mat...@li...; Mayer Gerhard
Betreff: Re: [Matplotlib-users] French characters
I think you'd have to add \acute to the overunder dictionary in =
mathtext.py and then use as '\acute{e}'. That assumes that a "`"
is close enough for the accent mark. If so, it's possible that other =
accent marks as well, though I don't see how to get an umlaut or =
cedilla.
As a general question, can mathtext directly access characters in the =
TeX font tables? Would that simply involve adding more entries to =
latex_to_bakoma in _mathtext_data.py??? If so, that might make it =
easier to reproduce many of the TeX accents (including umlaut), as the =
double-dot and acute marks have actual places in the font tables. It =
migh also make \AA (\Angstrom) less of a corner case.
--Matt
On 2005年1月11日, Mayer Gerhard wrote:
> Hi all,
> I cannot figure out howto use french characters using the Agg backend. =
> E.g. title(r'$Temp \acute e rature$') does not work.
> Has anyone an idea howto do it?
> Gerhard
>=20
>=20

I think you'd have to add \acute to the overunder dictionary in
mathtext.py and then use as '\acute{e}'. That assumes that a "`"
is close enough for the accent mark. If so, it's possible that
other accent marks as well, though I don't see how to get an
umlaut or cedilla.
As a general question, can mathtext directly access characters in
the TeX font tables? Would that simply involve adding more
entries to latex_to_bakoma in _mathtext_data.py??? If so, that
might make it easier to reproduce many of the TeX accents
(including umlaut), as the double-dot and acute marks have actual
places in the font tables. It migh also make \AA (\Angstrom) less
of a corner case.
--Matt
On 2005年1月11日, Mayer Gerhard wrote:
> Hi all,
> I cannot figure out howto use french characters using the Agg backend. 
> E.g. title(r'$Temp \acute e rature$') does not work.
> Has anyone an idea howto do it?
> Gerhard
> 
> 

HI again,
I have questions of how to generate new LUTs outside matplotlib.
3 main issues:
1/ how to create a new lut in the same way that cm.py/colors.py is doing it
 in matplotlib
2/ how to create a new lut which is given by a set of e.g., 256 colours 
levels (R, G, B)
 but not as a segmented array as in cm/colors
3/ How do you rescale a lut without rescaling the array itself?
(so an equivalent to load/itt log for example in Midas for those who know).
 For example I would like to use the jet lut but with a log increase
 of the lut so that e.g. displaying the color bar shows it is in ''log''
For 1, I am not so sure what to do, and for 2/ I give below
what I am doing at the moment. To be frank, it looks quite ugly
(mainly because I am a bad programmer and don't know so much about
python/matplotlib).
I got inspired by cm and colors.py and Midas lut
but really this is probably not the way to go.
In order to change the lut I just then do:
lut('mylut')
where 'mylut.lasc' is then the ascii file where the 256 colours are 
given in 3 columns
(R G B) of 256 rows
The problem is that since I do not have the corresponding segmented 
array for each
lut (and I don't want it to be that way) I need to define a ''dummy'' array.
Then each time I use imshow I must reload the lut (otherwise it uses 
this dummy segmented
array which is here a gray lut).
I am not sure this is all clear, but basically what I am trying to do 
here is to just
answer questions 1, 2, 3 above and below is an ugly solution for 2 (but 
incomplete).
Any help is welcome. Thanks.
Eric
#########################################################################################
"""######################################
 # MIDAS-LIKE LUT and ITT ??
 ######################################"""
_dummy_data = {'red': ((0., 0, 0), (1., 1, 1)),
 'green': ((0., 0, 0), (1., 1, 1)),
 'blue': ((0., 0, 0), (1., 1, 1))}
class myMidasLut(colors.LinearSegmentedColormap):
 """ Definition of luts a la Midas, with R, G, and B levels
 """
 def __init__(self, name='grey', alpha=1.0):
 self.LUT_PATH = '/softwares/python/pycral/midaslut/'
 self._red_lut = arange(256)/255.
 self._green_lut = arange(256)/255.
 self._blue_lut = arange(256)/255.
 self._isinit = True
 self.name = name
 self.N = 256
 cm.datad[name] = _dummy_data
 def new(self,name, alpha=1.0): 
 sname = str(name)
 sname = self.LUT_PATH+sname+".lasc"
 if os.path.isfile(sname):
 f = open(sname)
 list = f.readlines()
 for i in range(256):
 self._red_lut[i] = float(list[i].split()[0])
 self._green_lut[i] = float(list[i].split()[1])
 self._blue_lut[i] = float(list[i].split()[2])
 f.close
 self.name = name
 else :
 print 'ERROR: Lut file', name,'does not exist'
 rc('image', cmap=name)
 im = gci()
 if im is not None:
 im.set_cmap(self)
 im.set_alpha(alpha)
 draw_if_interactive()
 cm.datad[name] = _dummy_data
 
################ Default Lut initialisation ##
pglut = myMidasLut()
################ Function to change the lut ##
def lut (name, alpha=1.0) :
 pglut.new(name, alpha)
#########################################################################################
-- 
===============================================================
Observatoire de Lyon ems...@ob...
9 av. Charles-Andre tel: +33 4 78 86 83 84
69561 Saint-Genis Laval Cedex fax: +33 4 78 86 83 86
France http://www-obs.univ-lyon1.fr/eric.emsellem
===============================================================

Hi,
2 issues:
1/ just to remind you that I am still looking for a solution to the 
previously
mentioned bug in imshow (in terms of aspect='preserve').
2/ I have another problem with imshow:
When I do for example:
figure(1)
axes([-0.1,0,0.8,0.8])
myima = rand(50,50)
imshow(myima)
then it works and shows me the array with the axes partly outside the window
since the origin for the X axis is < 0
However if I do:
figure(1)
axes([0,-0.1,0.8,0.8])
myima = rand(50,50)
 imshow(myima)
with this time the Y origin < 0:
then I get a SEGMENTATION FAULT
??
thanks for any help there...
Eric
-- 
===============================================================
Observatoire de Lyon ems...@ob...
9 av. Charles-Andre tel: +33 4 78 86 83 84
69561 Saint-Genis Laval Cedex fax: +33 4 78 86 83 86
France http://www-obs.univ-lyon1.fr/eric.emsellem
===============================================================

>>>>> "James" == James Boyle <bo...@ll...> writes:
 James> if I run: PL.imshow(TArm,cmap = ML.cm.winter )
 James> PL.colorbar()
 James> I get the error listed at the end of this message:
Hi Jim,
What version of mpl are you using? With 0.70.1 I see no problems
 >>> from pylab import *
 >>> x = rand(12,12)
 >>> imshow(x, cmap=cm.winter)
 <matplotlib.image.AxesImage instance at 0x01476DC8>
 >>> colorbar()
 <matplotlib.axes.Axes instance at 0x01476EB8>
I did fix some colorbar bugs in 0.65.1. If your version is older than
this, it may explain the problem.
If you are using 0.70.1, please provide a little more information
about your environment, specifically a complete test script run with
the output of --verbose-helpful.
Hope this helps,
JDH

Hi all,
I cannot figure out howto use french characters using the Agg backend.=20
E.g. title(r'$Temp \acute e rature$') does not work.
Has anyone an idea howto do it?
Gerhard

if I run:
PL.imshow(TArm,cmap = ML.cm.winter )
PL.colorbar()
I get the error listed at the end of this message:
However if I run:
PL.imshow(TArm,cmap = ML.cm.winter,vmin=-50.,vmax=50.)
PL.colorbar()
Then all goes as expected - from where the code goes astray, it appears 
as if the autoscale limits are not being set???which is
circumvented if a specify the max and min explicitly.
Is this a problem? or am I missing something?
--Jim
/System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/ 
site-packages/matplotlib/pylab.py in colorbar(tickfmt)
 597 N = 200
 598
--> 599 c = linspace(cmin, cmax, N)
 600 C = array([c,c])
 601
/System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/ 
site-packages/matplotlib/mlab.py in linspace(xmin, xmax, N)
 73 def linspace(xmin, xmax, N):
 74 if N==1: return xmax
---> 75 dx = (xmax-xmin)/(N-1)
 76 return xmin + dx*arange(N)
 77
TypeError: unsupported operand type(s) for /: 'array' and 'int'

Thanks very much, Gary; that fixed it right off the bat.
Thanks,
Greg
On 2005年1月10日, Gary Ruben wrote:
> Another piece of info:
> Jonathan Brandmeyer on the numpy discussion list has built a version of
> Numeric for Python 2.4 and is temporarily hosting it until an official
> build is done. It's version 23.6 which is only 0.1 older than 23.7
> (according to my hp calculator):
> http://www4.ncsu.edu/~jdbrandm/Numeric-23.6.win32-py2.4.exe
>
> Gary R.

Hi,
TkAgg backend works fine except a corner case with the zoom button.
Consider with simple code :
from pylab import *
A = rand(1000,1000)
imshow(A,interpolation=Nearest)
When I zoom 3 or 4 times on the resulting image using the backend zoom 
button, I get an all white image from a certain zoom level (i.e. from 
factor of 100).
It is clearly a corner case but I sometime have to zoom on very fine 
details.
Consider this code in backend_bases.py :
 lastx, lasty, a, ind, lim, trans = self._xypress
 # ignore singular clicks - 5 pixels is a threshold
 if abs(x-lastx)<5 or abs(y-lasty)<5:
 self._xypress = None
 self.release(event)
 self.draw()
 return
I think we could decrease the threshold down to 1 pixel. Please tell me 
if it is incompatible with another piece of code.
Selecting a less than 1*1 (or 2*2) pixels area should do nothing (and 
not produce a blank image).
Cheers,
Xavier.

Another piece of info:
Jonathan Brandmeyer on the numpy discussion list has built a version of Num=
eric for Python 2.4 and is temporarily hosting it until an official build i=
s done. It's version 23.6 which is only 0.1 older than 23.7 (according to m=
y hp calculator):
http://www4.ncsu.edu/~jdbrandm/Numeric-23.6.win32-py2.4.exe
Gary R.
----- Original Message -----
From: "Greg Wilson" <gvw...@cs...>
To: mat...@li...
Subject: [Matplotlib-users] matplotlib / Python 2.4 / Numarray
Date: Sun, 9 Jan 2005 11:22:33 -0500
>=20
> Hi folks. Just setting up a new machine with Python 2.4, and wanted to
> check something. Under "Installing on Windows", the Matplotlib pages at
> sf.net say:
>=20
> For standard python installations, you will also need to install
> either Numeric or numarray in addition to the matplotlib installer.
> matplotlib provides installers for Numeric and numarray users. It is
> important that you pick the matplotlib installer that corresponds to
> your array package. Ie, if you mostly work with numarray arrays, use
> the matplotlib numarray installer. matplotlib has a numerix setting =
in
> the matplotlib rc file (which by default resides in
> c:\python23\share\matplotlitb\.matplotlibrc) and you should make sure
> this setting corresponds to your preferred array package.
>=20
> However, the download page:
>=20
>=20=わ20=わ20=わ20=わ20=わ20
> http://sourceforge.net/project/showfiles.php?group_id=3D80706&package_id=
=3D82474
>=20
> only differentiates installers by Python version; there's no hint which
> one is for Numpy, numarray, etc. The one I grabbed
> (matplotlib-0.70.1-win32.py2.4.exe) installed, but complains about not
> being able to find numarray (which is installed, for Python 2.4). I'd be
> happy to use Numpy, but the only releases available are for Python 2.3.
>=20
> Any suggestions?
>=20
> Thanks,
> Greg Wilson
>=20
>=20
> -------------------------------------------------------
> The SF.Net email is sponsored by: Beat the post-holiday blues
> Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
> It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
--=20
___________________________________________________________
Sign-up for Ads Free at Mail.com
http://promo.mail.com/adsfreejump.htm

>>>>> "Todd" == Todd Miller <jm...@st...> writes:
 Todd> I verified that matplotlib-0.70 works w/ numarray-1.1.1 on
 Todd> Windows XP using a quick "plot([1,2,3,4]); show();" test. I
 Todd> noted that TkAgg is now raising an exception when the plot
 Todd> window is closed, but the plot looked fine to me.
Thanks Todd -- fixed in CVS. This resulted from generating a location
event before the mouse was over the figures, and hence event.x and
event.y were None and downstream in the code this condition was
accounted for.
JDH

I verified that matplotlib-0.70 works w/ numarray-1.1.1 on
Windows XP using a quick "plot([1,2,3,4]); show();" test. I
noted that TkAgg is now raising an exception when the plot
window is closed, but the plot looked fine to me.
Cheers,
Todd
Exception in Tkinter callback
Traceback (most recent call last):
 File "h:\python24\lib\lib-tk\Tkinter.py", line 1345, in __call__
 return self.func(*args)
 File
"H:\python24\lib\site-packages\matplotlib\backends\backend_tkagg.py",
lin
e 215, in key_release
 FigureCanvasBase.key_release_event(self, key)
 File
"H:\python24\lib\site-packages\matplotlib\backend_bases.py",
line 677, in
 key_release_event
 event = KeyEvent('key_release_event', self, key,
self._lastx, self._lasty)
 File
"H:\python24\lib\site-packages\matplotlib\backend_bases.py",
line 640, in
 __init__
 LocationEvent.__init__(self, name, canvas, x, y)
 File
"H:\python24\lib\site-packages\matplotlib\backend_bases.py",
line 566, in
 __init__
 if a.in_axes(self.x, self.y):
 File "H:\python24\lib\site-packages\matplotlib\axes.py",
line 1544, in in_axes
 return self.bbox.contains(xwin, ywin)
TypeError: float() argument must be a string or a number

>>>>> "Darren" == Darren Dale <dd...@co...> writes:
 Darren> I think the "Installing on Windows" note is out of
 Darren> date. Recently, the MPL dev's changed the install code to
 Darren> automatically detect numarray and Numeric, and to install
 Darren> accordingly. This is why you dont see an installer
 Darren> specifically for numarray or numeric.
Yep, that's right. Perhaps someone else can verify that matplotlib
with numerux : numarray works on python2.4 / win32 just to verify that
I didn't screw up the 2.4 installer.
 Darren> As for solving your problem, I don't have an answer but
 Darren> let me offer a couple suggestions. Can you import numarray
 Darren> from an interactive python session? Could you try to
 Darren> temporarily install Numeric, and see if MPL can install?
Also verify that your http://matplotlib.sf.net/.matplotlibrc setting
for numerix is numarray. While testing, you may want to run with
--verbose-helpful which may provide some additional diagnoistic
information. Note you can also select numeric vs numarray from the
DOS shell, which can be helpful while debugging this problem
 c:> python myscript.py --verbose-helpful --Numeric
 c:> python myscript.py --verbose-helpful --numarray
Hope this helps,
JDH

I'm new to both Python and matplotlib.
I'm using this on MS Win with Python 2.3 and matplotlib 0.7. and ipython 
as IDE.
A substantial amount of memory is allocated when a array of constantly 
varying values is plotted, as example:
# Sawtooth signal 32768 elements long to show memory usage.
y = ones(2**15)
y[1::2] = 0
plot(y)
if the figure created is now killed, the memory is not released, and 
more memory is allocated each time the plot() command is executed. Thr 
memory is only returned to the system once python is closed.
Plotting a signal with less amplitude variation or slow amplitude change 
( for instance plot(ones2**15) or plot(sin(arange(0,10,10./2**15)) ) 
uses a lot less memory, so the leak is not as obvious, but still there.
Any suggestions from the group on resolving this?
Thanks,
Hennie

Hi Greg,
> Hi folks. Just setting up a new machine with Python 2.4, and wanted to
> check something. Under "Installing on Windows", the Matplotlib pages at
> sf.net say:
>
> For standard python installations, you will also need to install
> either Numeric or numarray in addition to the matplotlib installer.
> matplotlib provides installers for Numeric and numarray users. It is
> important that you pick the matplotlib installer that corresponds to
> your array package. Ie, if you mostly work with numarray arrays, use
> the matplotlib numarray installer. matplotlib has a numerix setting in
> the matplotlib rc file (which by default resides in
> c:\python23\share\matplotlitb\.matplotlibrc) and you should make sure
> this setting corresponds to your preferred array package.
>
> However, the download page:
>
> 
> http://sourceforge.net/project/showfiles.php?group_id=80706&package_id=8247
>4
>
> only differentiates installers by Python version; there's no hint which
> one is for Numpy, numarray, etc. The one I grabbed
> (matplotlib-0.70.1-win32.py2.4.exe) installed, but complains about not
> being able to find numarray (which is installed, for Python 2.4). I'd be
> happy to use Numpy, but the only releases available are for Python 2.3.
>
> Any suggestions?
>
I think the "Installing on Windows" note is out of date. Recently, the MPL 
dev's changed the install code to automatically detect numarray and Numeric, 
and to install accordingly. This is why you dont see an installer 
specifically for numarray or numeric.
As for solving your problem, I don't have an answer but let me offer a couple 
suggestions. Can you import numarray from an interactive python session? 
Could you try to temporarily install Numeric, and see if MPL can install?
Darren

Hi folks. Just setting up a new machine with Python 2.4, and wanted to
check something. Under "Installing on Windows", the Matplotlib pages at
sf.net say:
 For standard python installations, you will also need to install
 either Numeric or numarray in addition to the matplotlib installer.
 matplotlib provides installers for Numeric and numarray users. It is
 important that you pick the matplotlib installer that corresponds to
 your array package. Ie, if you mostly work with numarray arrays, use
 the matplotlib numarray installer. matplotlib has a numerix setting in
 the matplotlib rc file (which by default resides in
 c:\python23\share\matplotlitb\.matplotlibrc) and you should make sure
 this setting corresponds to your preferred array package.
However, the download page:
 http://sourceforge.net/project/showfiles.php?group_id=80706&package_id=82474
only differentiates installers by Python version; there's no hint which
one is for Numpy, numarray, etc. The one I grabbed
(matplotlib-0.70.1-win32.py2.4.exe) installed, but complains about not
being able to find numarray (which is installed, for Python 2.4). I'd be
happy to use Numpy, but the only releases available are for Python 2.3.
Any suggestions?
Thanks,
Greg Wilson

Andrew Straw wrote:
> Stephen Walton wrote:
>
>> Line 851 in pylab.py should change from
>>
>> line = line[:line.rfind('%')].strip()
>>
>> to
>>
>> line = line[:line.find('%')].strip()
>>
>
> Done.
Cool, thanks.
> Now maybe someone can contribute a patch for 3D plots while John is in 
> Brazil as a sign of our appreciation. :)
Based on what I've read around here, implementing 3D plots is going to 
require more than a simple patch.

I noticed a memory leak when using imshow with the TkAgg backend (the 
Agg backend seems to be OK). Below is the system information and the 
result of running the memory leak script provided in the FAQ. I use 
Numeric for my work, but numarray is also installed.
localhost:src$ python2.3
Python 2.3.4 (#1, Oct 31 2004, 10:10:53)
[GCC 3.2.2 20030222 (Red Hat Linux 3.2.2-5)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
 >>> import numarray
 >>> numarray.__version__
'1.1'
 >>> import Numeric
N>>> Numeric.__version__
'23.5'
 >>> import pylab
 >>> import matplotlib
 >>> matplotlib.__version__
'0.70.1'
Output from memory leak checker script:
0 52632 17192
1 58484 18679
2 64180 20126
3 70000 21610
4 75772 23009
5 81564 24474
6 87272 25923
7 92988 27372
8 98684 28817
9 104456 30213
10 110160 31662
11 115956 33142
12 121764 34626
13 127468 36008
14 133172 37456
15 138968 38921
16 144748 40385
17 150444 41766
18 156132 43211
19 161816 44657
20 167516 46104
21 173204 47547
22 179008 48966
23 184676 50409
24 190372 51856
25 196060 53300
26 201764 54684
27 207536 56146
28 213240 57594
29 218948 59041
30 224616 60487
31 230288 61866
32 235964 63308
33 241664 64757
34 247444 66219
35 253248 67636
36 259024 69099
37 264712 70544
38 270408 71993
39 276084 73370
40 281780 74817
41 287568 76294
42 293260 77739
43 298960 79185
44 304648 80565
45 310352 82014
46 316100 83470
47 321792 84917
48 327452 86295
49 333236 87775
50 338928 89220
51 344728 90686
52 349444 92103
53 350840 93551
54 341692 95015
55 332648 96494
56 326660 97955
57 327812 99332
58 330168 100774
59 331612 102224
60 333080 103667
61 334524 105048
62 336444 106532
63 338144 107995
64 340060 109454
65 340968 110837
66 339636 112286
67 340340 113725
68 340984 115174
69 343468 116555
70 344244 118001
71 344456 119450
72 346036 120912
73 345808 122377
74 346944 123775
75 348400 125255
76 350128 126717
77 349552 128173
78 348952 129568
79 348036 131014
80 347556 132461
81 349000 133907
82 348828 135288
83 348528 136733
84 348156 138199
85 348420 139639
86 346460 141083
87 349312 142465
88 348832 143926
89 348404 145373
90 349888 146851
91 349780 148229
92 348632 149677
93 348748 151137
94 348040 152619
95 347016 154001
96 347108 155466
97 348496 156905
98 350300 158349
99 351956 159766
100 353368 161212
101 351320 162659
102 353216 164121
103 352952 165569
104 353652 166952
105 353256 168411
106 352088 169873
107 354428 171309
108 353440 172691
109 356004 174173
110 356008 175613
111 354096 177074
112 356036 178458
113 356228 179923
114 358000 181403
115 358012 182847
116 358220 184296
117 359524 185697
118 357732 187143
119 357580 188580
120 355680 190024
121 356336 191433
122 356676 192913
123 358288 194362
124 356352 195808
125 356684 197208
126 357296 198689
127 358940 200155
128 361464 201602
129 360752 203045
130 360148 204462
131 362032 205908
132 364036 207397
133 365656 208836
134 365360 210217
135 361592 211675
136 364828 213122
137 365600 214567
138 365184 215961
139 370880 217425
140 362380 218872
141 366444 220319
142 362832 221785
143 366424 223164
144 363908 224630
145 363980 226076
146 369004 227524
147 371348 228907
148 370072 230353
149 371484 231799
Average memory consumed per loop: 1427.6000k bytes
Thanks!
--
Jeff

Andrew Straw wrote:
> So, I offer the following patch [2] to pylab.py which fixes this. I 
> hereby ask for your feedback indicating if you are happy with the 
> current behavior, or if you prefer that pylab does not override 
> builtins. (Also, if you have a better way, that would be appreciated, too.)
+1 on your patch.
I'd also much rather have the builtin namespace be left alone.
Cheers,
f

A few weeks ago (on Dec 18), I send an email to the matplotlib-devel 
list indicating that "from pylab import *" overrides some builtin 
functions, such as min() and max(). [1]
This results from pylab enlarging its namespace greatly with statements 
like "from numerix import *" and "from mlab import *". In general this 
is a good thing, but it seems numarray.linear_algebra.mlab (amongst 
possibly others) overrides some builtin names. Although I don't see the 
benefit in this design for numarray.linear_algebra.mlab, I can live with 
it, since I never do "from numarray.linear_algebra.mlab import *". 
However, I (and many others here, I suspect) would like to frequently 
use "from pylab import *", and it really pisses me off when I discover 
that various builtins are overridden, causing mysterious errors that may 
be hard to track down.
So, I offer the following patch [2] to pylab.py which fixes this. I 
hereby ask for your feedback indicating if you are happy with the 
current behavior, or if you prefer that pylab does not override 
builtins. (Also, if you have a better way, that would be appreciated, too.)
You may check your own systems using a little script I wrote while 
testing this. [3]
Cheers!
Andrew
[1] 
http://sourceforge.net/mailarchive/forum.php?thread_id=6190717&forum_id=36187
[2] Patch to pylab.py, to be inserted anywhere after the last "from blah 
import *", e.g. line 216.
# restore builtin functions which may have been overridden
min = getattr(sys.modules['__builtin__'],'min')
max = getattr(sys.modules['__builtin__'],'max')
sum = getattr(sys.modules['__builtin__'],'sum')
round = getattr(sys.modules['__builtin__'],'round')
abs = getattr(sys.modules['__builtin__'],'abs')
[3] Script to test for overriding of builtin names:
import sys
def check_globals():
 for key in globals().keys():
 if key in dir(sys.modules['__builtin__']):
 if globals()[key] != getattr(sys.modules['__builtin__'],key):
 print "'%s' was overridden in globals()."%key
print 'before pylab import'
check_globals()
print
from pylab import *
print 'after pylab import'
check_globals()
print

Howdy,
We just installed matplotlib version 0.70.1 on a new computer, and some
code I wrote broke which was written for matplotlib 0.61. 
The code I used that broke was:
from time import time
from matplotlib.matlab import *
with the later version of matplotlib this became:
from time import time
from matplotlib.pylab import *
and this doesn't work because pylab exposes time as a module. Now I
realize this is not necessarily good programming style :-). But I am
using about 20 different pylab commands. So the question is, should
pylab be more careful about what it exposes?
thanks,
Danny 
		
__________________________________ 
Do you Yahoo!? 
All your favorites on one personal page – Try My Yahoo!
http://my.yahoo.com