Thomas Kluyver

You've installed a kernelspec at some point which points to the other environment. Run `jupyter kernelspec list` to see where it is. If you delete it, it should fall back...

Have you installed Jupyter in the env you're talking about?

Can you look at the `kernel.json` in each of those kernelspec directories you found?

This looks similar to jupyter/jupyter#270 . Ping @minrk - I think this is due to installing kernelspecs automatically as data files in the wheel.

For now, you can probably work around it by changing the first item in `argv` to 'python3' in the Python 3 kernel.json file.

Hopefully not. We've refined this behaviour in a new version of `jupyter_client`

It's not clear if there's anything for us to do here. Maybe you're just running something that takes a while? There's no obvious reason that the notebook should make execution...

A few people have reported slowdowns in completions with IPython 6.0 (which made some changes to the completion machinery). Can you double check `IPython.__version__`?

Weird, I don't know why that would affect completion.

I think you may be describing a number of different slowdowns under this one issue - the original was a slowdown running code, and other people have described slow completion,...