[IPython-User] ipython package import mechanism exhibits different behaviour

Antony Lee antony.lee@berkeley....
Mon Jul 30 12:05:41 CDT 2012


Out of curiosity, when is the path "set up to include the working
directory"? I thought that was Python's default behaviour, but apparently
not?
Antony

2012/7/30 Thomas Kluyver <takowl@gmail.com>

> On 30 July 2012 09:03, Antony Lee <antony.lee@berkeley.edu> wrote:
> > Is that behaviour a bug, or documented somewhere?
>
> It looks like a bug, and I think it's specific to numpy.
>
> Something in the startup of IPython must be importing numpy before it
> sets up the path to include the working directory, so it gets the
> system copy instead of the local copy. That will also be slowing down
> startup.
>
> A look in sys.modules suggests that we're also loading simplejson,
> paramiko, multiprocessing and unittest, none of which I think we need
> for regular use. I'll investigate.
>
> Thomas
> _______________________________________________
> IPython-User mailing list
> IPython-User@scipy.org
> http://mail.scipy.org/mailman/listinfo/ipython-user
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.scipy.org/pipermail/ipython-user/attachments/20120730/0136665d/attachment.html 


More information about the IPython-User mailing list