[Numpy-discussion] Cutting 1.0.2 release

Fernando Perez fperez.net at gmail.com
Wed Jan 31 11:31:48 CST 2007


On 1/31/07, Gary Ruben <gruben at bigpond.net.au> wrote:
> Actually, I just realised; it's not an ipython problem. I think it's a
> matplotlib problem. I'll report it there.

Until mpl drops support for the compatibility layers, you may want to
set up a simple pylab profile.  In ~/.ipython make a file called
'ipythonrc-pylab' consisting of:

#######
# Load default config
include ipythonrc

# Add single-line python statements here
execute from numpy import *
########

Since pylab does a 'from .num?. import *' this will ensure that the
top-level visible functions are the current numpy ones, not the
compatibility layer ones.  You then start things with:

ipython -pylab -p pylab

and you'll get:

In [1]: zeros?
Type:           builtin_function_or_method
Base Class:     <type 'builtin_function_or_method'>
Namespace:      Interactive
Docstring:
    zeros((d1,...,dn),dtype=float,order='C')

    Return a new array of shape (d1,...,dn) and type typecode with all
    it's entries initialized to zero.



Not ideal, but it's a little hack that will work in practice until we
finish crossing the muddy river of backwards compatibility.

Cheers,

f


More information about the Numpy-discussion mailing list