I wonder if I've misunderstood or made a mistake? I renamed a file:
/usr/lib/python2.5/new.py to /usr/lib/python2.5/new.bak
and everything worked... but now, after logging out and logging back in
again, I'm getting the problem again?
Perhaps that was the standard libraries module? But I cannot
I'm revisiting this with a new round of errors. I keep getting this error,
maybe related as before to the 'new' module, but I cannot tell?? Does anyone
know what is going on?
Python 2.5.1 (r251:54863, Jun 15 2008, 18:24:51)
[GCC 4.3.0 20080428 (Red Hat 4.3.0-8)] on linux2
Type help, copyright,
John [H2O] wrote:
I wonder if I've misunderstood or made a mistake? I renamed a file:
/usr/lib/python2.5/new.py to /usr/lib/python2.5/new.bak
and everything worked... but now, after logging out and logging back in
again, I'm getting the problem again?
Perhaps that was the standard
John wrote:
Hello, could someone please help me understand a strange problem,
possibly associated with PYTHONPATH. When I import matplotlib, pylab, or
scipy from any directory other than the root installation directory, it
fails. However, if I'm in the python installation directory there
Hello, could someone please help me understand a strange problem, possibly
associated with PYTHONPATH. When I import matplotlib, pylab, or scipy from
any directory other than the root installation directory, it fails. However,
if I'm in the python installation directory there are no errors. Thanks
