I just noticed pylab.load now points to np.load when it used to point
to mlab.load
In [17]: import pylab
In [18]: import numpy
In [19]: pylab.load is numpy.load
Out[19]: True
This may have been Eric's change to clean up the pylab imports -- all
the mlab imports come before the pylab imports. Was this intentional?
My guess is not, since np.loadtxt is the replacement for pylab.load.
I prefer to do what we are currently doing, which is issue the
deprecation warning, but I wanted to at least find out if this change
was intentional (I noticed it because it broke
docs/pyplot/plotmap.py), which tries to load some basemap data:
In [12]: x =
pylab.load('/home/jdhunter/python/svn/matplotlib/trunk/htdocs/screenshots/data/etopo20data.gz')
---------------------------------------------------------------------------
IOError Traceback (most recent call last)
/home/jdhunter/mpl99/doc/api/<ipython console> in <module>()
/home/jdhunter/dev/lib/python2.5/site-packages/numpy/lib/io.pyc in
load(file, mmap_mode)
199 except:
200 raise IOError, \
--> 201 "Failed to interpret file %s as a pickle" % repr(file)
202
203 def save(file, arr):
JDH
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Matplotlib-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
