Error when trying to import ipykernel: No module named 'IPython.paths'

[astrofrog]

I am trying to import ipykernel and getting the following error:

In [10]: import ipykernel
---------------------------------------------------------------------------
ImportError                               Traceback (most recent call last)
<ipython-input-10-280cf9cbe7f8> in <module>()
----> 1 import ipykernel

/Users/tom/miniconda3/envs/production/lib/python3.4/site-packages/ipykernel/__init__.py in <module>()
      1 from ._version import version_info, __version__
----> 2 from .connect import *

/Users/tom/miniconda3/envs/production/lib/python3.4/site-packages/ipykernel/connect.py in <module>()
     11 
     12 from IPython.core.profiledir import ProfileDir
---> 13 from IPython.paths import get_ipython_dir
     14 from ipython_genutils.path import filefind
     15 from ipython_genutils.py3compat import str_to_bytes

ImportError: No module named 'IPython.paths'

Here are the versions I'm using:

ipykernel==4.0.3
ipython==4.0.0
ipython-genutils==0.1.0
jupyter-client==4.0.0
jupyter-console==4.0.0
jupyter-core==4.0.4
path.py==0.0.0
pyzmq==14.7.0
traitlets==4.0.0

This is with Python 3.4

[astrofrog]

Sorry, I think there was a strange issue with my conda environments, this is no longer an issue for me.

[jakirkham]

Do you remember what caused this @astrofrog?

[brockk]

@jakirkham I just got this same message when sending a task to an ipengine running on machine with old IPython (v3 perhaps) connected to an ipcontroller running on a machine with new IPython (v4). The engine registers with the controller ok, but when I do

view.map_sync(do_thing, [1,2,10])

and one of the jobs goes to the engine on the old machine, I get the error message.