matplotlib-devel Mailing List for matplotlib

Hi,
I wrote a random walk program which you will find below. When I run it from the terminal, it gives error which I am not able to figure out what could be wrong. From the bash shell, I give a command 
 >python2.4 random.py
It gives error:
-----------------------------------------------------------------------------------------
 Traceback (most recent call last):
 File "random.py", line 2, in ?
 from pylab import *
 File "/usr/lib/python2.4/site-packages/pylab.py", line 1, in ?
 from matplotlib.pylab import *
 File "/usr/lib/python2.4/site-packages/matplotlib/pylab.py", line 196, in ?
 import mlab #so I can override hist, psd, etc...
 File "/usr/lib/python2.4/site-packages/matplotlib/mlab.py", line 58, in ?
 import sys, random
 File "/home/ofenerci/workspace/random.py", line 11, in ?
 if (rand() > 0.5):
NameError: name 'rand' is not defined
[3] Done gedit random.py
-------------------------------------------------------------------------------------------------------------
When I write the program step by step inside the python shell or run it inside the python-idle, everything goes smoothly and it doesn't give any error. I don't know why gives error, If I run it from the terminal.
thanks,
Ahmet Nurlu
Random.py Program:
---------------------------------------------------------------------------
from pylab import *
npts=1000
nplot=10
for i in range(0,nplot):
 
 xplot=[]
 x=0.0
 for i in range(0,npts):
 if (rand() > 0.5):
 x=x+1
 else:
 x=x-1
 xplot.append(x)
 plot(xplot,'g')
 hold(True)
show()
-------------------------------------------------------------------------
		
---------------------------------
Relax. Yahoo! Mail virus scanning helps detect nasty viruses!

>>>>> "James" == James Evans <jre...@ea...> writes:
 James> The patch is as follows: -- In several places arrays are
 James> initialized with a variable for the length. As per
 James> Stroustrup arrays can only be specified with constants or
 James> using 'new' .
Hey James, I notice you have 3 patches with the title 
 Strict C/C++ Conformance
Have all of these been resolved by the patch Andrew applied? If so,
I'll close them.
Thanks,
JDH

>>>>> "Jordan" == Jordan Dawe <jdawe@u.washington.edu> writes:
 Jordan> I've uploaded a patch to sourceforge that lets you control
 Jordan> the grid line attributes from the grid() function. So,
 Jordan> for instance, if you wanted red grid lines on one plot,
 Jordan> you can go grid(color='r')
Thanks Jordan, nicely done. I've committed this to svn revision 2159.
For all of the matplotlib developers (or potential developers!) out
there, we've fallen a bit behind on applying the sf patches and
resolving the reported bugs. Everyone try to pick a few off as you
have time.
Thanks,
JDH

>>>>> "Jos=E9" =3D=3D Jos=E9 Matos <jao...@gm...> writes:
 Jose> IMO rpm is right and the test is wrong. It does not make
 Jose> any sense to require a running X just to check that pygtk is
 Jose> installed.
In principle, I certainly agree with you. In practice, I think this
is harder than it sounds, because several of us have tried to make a
build/configure system that 1) works and 2) doesn't require X, and
obviously we have failed. Whle it certainly must be possible, we
clearly haven't found the right apporaches for GTK* and Tk*.
 >> The mysterious part is why bdist_rpm /used/ to work for mpl as
 >> of 0.83.2. It could be either that a change in mpl's build
 >> made it more sensitive to X11 issues than before, or that
 >> Fedora3 updated its rpm build scripts between those days and
 >> today, and that now they do this 'unset DISPLAY'. But given
 >> that on Ubuntu and Mandriva it's working OK, I wouldn't worry
 >> too much about it. Having that feedback was a good outcome of
 >> this thread, even if I can't upgrade in our lab :)
 Jose> The usual trick in rpms it to require a nest X to test for
 Jose> pygtk.
I'm not sure I understand this. We have the following
if BUILD_GTK:
 try:
 import gtk
 except ImportError:
 print 'GTK requires pygtk'
 BUILD_GTK=3D0
 except RuntimeError:
 print 'pygtk present but import failed'
The ImportError is designed to catch the case where pygtk is not
present and the RuntimeError is designed to warn but not fail if X is
not present. I'll do some testing tonight to see if I can isolate
where this is failing. =20
JDH