[IPython-User] ipython package import mechanism exhibits different behaviour
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
2012/7/30 Thomas Kluyver <firstname.lastname@example.org>
> On 30 July 2012 09:03, Antony Lee <email@example.com> 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
> 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.
> IPython-User mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the IPython-User