[IPython-dev] Notebooks enforce specific kernel

[Thomas Kluyver]

On 29 June 2015 at 10:54, MinRK <benjaminrk at gmail.com> wrote:

> I realize there's an issue with IPython's attempts to pseudo-activate a
> virtualenv if one is found but IPython isn't using it. If the notebook
> server is in an env and the kernel isn't, the kernel will try to activate
> the server's env (right?). Should we:
>
> 1. remove the attempts to activate envs
> 2. pop VIRTUAL_ENV from the env passed down to kernels
>

I think we should probably still check the virtualenv when you start
terminal IPython, but it doesn't make sense for the notebook. What I'm not
sure about is the zmq terminal console and Qt console. It's technically
easiest to draw the line between the kernel and the single-process
interface, but it might be surprising that the zmq consoles behave
differently in that regard from the plain terminal interface.

Thomas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/ipython-dev/attachments/20150629/6caebe6e/attachment.html>