Run Cell does not find Jupyter in virtual environment

[mrvkino]

Environment data

• VS Code version: 1.29.1
• Extension version (available under the Extensions sidebar): 2018.11.0
• OS and version: MacOSX 10.14.1
• Python version (& distribution if applicable, e.g. Anaconda): homebrew python 3.7.1
• Type of virtual environment used (N/A | venv | virtualenv | conda | ...): pipenv
• Relevant/affected Python packages and their versions: jupyter notebooks

Actual behavior

Notification with the message: Running cells requires Jupyter notebooks to be installed.

I am able to start jupyter notebook in my virtual environment.

Expected behavior

Jupyter Notebook being started.

Steps to reproduce:

1. Create a jupyter python file
2. Click the Run Cell

Logs

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

Microsoft Python Language Server version 0.1.65.0
Initializing for /Users/.../.local/share/virtualenvs/jupyter_vscode-_1tZN8jX/bin/python

Linter 'flake8' is not installed. Please install it or select another linter".
Error: Module 'flake8' not installed.

Output from Console under the Developer Tools panel (toggle Developer Tools on under Help)

In the console of the Developper Tools I see that the plug-in is looking for Jupyter in a bunch of my pyenv Python but not my virtualenv.

[rchiodo]

Looks like pip venv isn't working. We don't find the activate script.

Could you possibly try the insiders build? I added some support for finding the activate script that isn't in the build you're using yet..

[mrvkino]

I Installed the insider build in a clean install of VSCode Insider v1.30.0 (to prevent issue with my day-to-day VSCode).

If I start VSCode after I started my venv it works.

pipenv shell

And then call:

code-insidesr .

The run cell works.

If I start VSCode outside of the venv, it detects the venv from the Pipfile, but is not able to find Jupyter.

[rchiodo]

Okay thanks. That helps. Looks like virtual pipenvs aren't supported yet then.

[mrvkino]

Ha! I thought since the plugin could find the Pipenv and start it automatically when starting a shell it would do the same for the Jupyter Notebook.

Thanks, really happy to be able to work on my notebook in VSCode. Hope the support for Pipenv comes soon.

[rchiodo]

Seems that pyenv-virtualenv also has the same problem. Likely we need to find the activate script for other virtual environments besides conda.

[kvdveer]

This is the workaround I'm using:

Run this as the first cell:

#%% Activate virtualenv

virtualenv_path = "./.venv"
exec(
    open("%s/bin/activate_this.py" % virtualenv_path).read(), 
    dict(__file__="%s/bin/activate_this.py" % virtualenv_path)
)

This will only work correctly if ipython and your venv use the same python binary.

[rchiodo]

Don's work on microsoft/vscode-python#3330 is a precursor to getting this working.

[AlJohri]

@rchiodo Hi, I just ran into this error as well via a pipenv virtual environmnent after clicking "Run Cell". It's not working even if I start code . within the virtualenv.

I'm using PIPENV_VENV_IN_PROJECT=true so the virtualenv is storied in the .venv folder. The python path is set in settings.json.

"python.pythonPath": ".venv/bin/python",

I've verified that jupyter is definitely installed within the virtualenv and up to date as per these instructions.

For some reason the debug console starts iterating through the other installed pythons versions? As you can see in the screenshot below, it starts with the correct python in the .venv folder and then iterates through my other pythons.

[rchiodo]

We need to 'activate' the virtual env prior to running jupyter. Right now we're just using the same python.

The other jupyters running is us searching for one that will work. We don't actually need the same environment to start jupyter, we just need to point it at the correct one (see jupyter kernel specs).

Although now that we know we need to activate it, this will likely change too, as I doubt Jupyter/iPython activates the virtual environment before using it.

[AlJohri]

@rchiodo I see. So selecting a python interpreter won't also activate the virtualenv? I feel as though this worked in the past when I was regular pipenv without setting PIPENV_VENV_IN_PROJECT=true.

Is there some special handling for pipenv that activate the virtualenv that is no longer being run now that I'm using the .venv/bin/python?

[rchiodo]

Selecting a python interpreter doesn't run the pipenv shell command. At least not yet. That's the change we're working on. It never did. We simply run the python within the same directory. (The one that pipenv install creates/copies)

However if you run vscode from within the pipenv shell, it should work. That's the new part that I'm not sure why it isn't working for you.

[rchiodo]

This should be fixed now in our insider's build (well in about half an hour after the build updates).

Please let me know if it isn't. Thanks.