“Running cells requires Jupyter notebooks to be installed” error in VS Code
up vote
3
down vote
favorite
I'm trying to use the new Jupyter integration for the Python extension in VS Code, and I'm getting the above error even though I have Jupyter installed and it works fine from the command prompt.
Here's my environment:
- Python extension version 2018.10.1, and I see
Run Cell/Run All Cellstooltips above#%%comments. - I've used the Python:
Select Interpretercommand to select my Anaconda environment, which is at~/AppData/Local/Continuum/anaconda3/python.exe. - I have Jupyter installed in that interpreter (jupyter.exe is in the Scripts sub-folder under that location), and it runs fine with the
jupyter notebookcommand at the Anaconda prompt.
But whenever I click on Run Cell or press shift-enter, I get this error message:
"Running cells requires Jupyter notebooks to be installed." Source: Python (Extension)
Is there something else I need to do to configure this?
visual-studio-code
asked Nov 11 at 1:14
Doug Mahugh
37428
add a comment |
up vote
3
down vote
favorite
I'm trying to use the new Jupyter integration for the Python extension in VS Code, and I'm getting the above error even though I have Jupyter installed and it works fine from the command prompt.
Here's my environment:
- Python extension version 2018.10.1, and I see
Run Cell/Run All Cellstooltips above#%%comments. - I've used the Python:
Select Interpretercommand to select my Anaconda environment, which is at~/AppData/Local/Continuum/anaconda3/python.exe. - I have Jupyter installed in that interpreter (jupyter.exe is in the Scripts sub-folder under that location), and it runs fine with the
jupyter notebookcommand at the Anaconda prompt.
But whenever I click on Run Cell or press shift-enter, I get this error message:
"Running cells requires Jupyter notebooks to be installed." Source: Python (Extension)
Is there something else I need to do to configure this?
visual-studio-code
asked Nov 11 at 1:14
Doug Mahugh
37428
I'm seeing the exact same thing (except I'm not using Anaconda)
– David Waterworth
Nov 12 at 9:00
I've had a similar problem. For me it worked with jupyter, when I enabled the base environment of my anaconda installation.
– alybel
Nov 12 at 10:45
Check that jupyter.exe is on your path - see my answer to a similar question here - stackoverflow.com/questions/52287117/…
– David Waterworth
Nov 12 at 21:45
I have the same problem, and I am using the base environment. Although I can runjupyter notebookeven from inside VS Code in a Python terminal. So it should be working. And adding it to the path completely defeats the purpose of environments, although I haven't tested whether that works. But it states on Microsofts pages that jupyter only needs to be installed in the environment, nothing about Path and whatever. I don't have python in my path and that works as well, obviously.
– clocktown
Nov 16 at 14:28
add a comment |
up vote
3
down vote
favorite
up vote
3
down vote
favorite
I'm trying to use the new Jupyter integration for the Python extension in VS Code, and I'm getting the above error even though I have Jupyter installed and it works fine from the command prompt.
Here's my environment:
- Python extension version 2018.10.1, and I see
Run Cell/Run All Cellstooltips above#%%comments. - I've used the Python:
Select Interpretercommand to select my Anaconda environment, which is at~/AppData/Local/Continuum/anaconda3/python.exe. - I have Jupyter installed in that interpreter (jupyter.exe is in the Scripts sub-folder under that location), and it runs fine with the
jupyter notebookcommand at the Anaconda prompt.
But whenever I click on Run Cell or press shift-enter, I get this error message:
"Running cells requires Jupyter notebooks to be installed." Source: Python (Extension)
Is there something else I need to do to configure this?
visual-studio-code
asked Nov 11 at 1:14
Doug Mahugh
37428
I'm trying to use the new Jupyter integration for the Python extension in VS Code, and I'm getting the above error even though I have Jupyter installed and it works fine from the command prompt.
Here's my environment:
- Python extension version 2018.10.1, and I see
Run Cell/Run All Cellstooltips above#%%comments. - I've used the Python:
Select Interpretercommand to select my Anaconda environment, which is at~/AppData/Local/Continuum/anaconda3/python.exe. - I have Jupyter installed in that interpreter (jupyter.exe is in the Scripts sub-folder under that location), and it runs fine with the
jupyter notebookcommand at the Anaconda prompt.
But whenever I click on Run Cell or press shift-enter, I get this error message:
"Running cells requires Jupyter notebooks to be installed." Source: Python (Extension)
Is there something else I need to do to configure this?
visual-studio-code
visual-studio-code
asked Nov 11 at 1:14
Doug Mahugh
37428
asked Nov 11 at 1:14
Doug Mahugh
37428
asked Nov 11 at 1:14
Doug Mahugh
37428
asked Nov 11 at 1:14
Doug Mahugh
37428
asked Nov 11 at 1:14
Doug Mahugh
37428
37428
I'm seeing the exact same thing (except I'm not using Anaconda)
– David Waterworth
Nov 12 at 9:00
I've had a similar problem. For me it worked with jupyter, when I enabled the base environment of my anaconda installation.
– alybel
Nov 12 at 10:45
Check that jupyter.exe is on your path - see my answer to a similar question here - stackoverflow.com/questions/52287117/…
– David Waterworth
Nov 12 at 21:45
I have the same problem, and I am using the base environment. Although I can runjupyter notebookeven from inside VS Code in a Python terminal. So it should be working. And adding it to the path completely defeats the purpose of environments, although I haven't tested whether that works. But it states on Microsofts pages that jupyter only needs to be installed in the environment, nothing about Path and whatever. I don't have python in my path and that works as well, obviously.
– clocktown
Nov 16 at 14:28
add a comment |
I'm seeing the exact same thing (except I'm not using Anaconda)
– David Waterworth
Nov 12 at 9:00
I've had a similar problem. For me it worked with jupyter, when I enabled the base environment of my anaconda installation.
– alybel
Nov 12 at 10:45
Check that jupyter.exe is on your path - see my answer to a similar question here - stackoverflow.com/questions/52287117/…
– David Waterworth
Nov 12 at 21:45
I have the same problem, and I am using the base environment. Although I can runjupyter notebookeven from inside VS Code in a Python terminal. So it should be working. And adding it to the path completely defeats the purpose of environments, although I haven't tested whether that works. But it states on Microsofts pages that jupyter only needs to be installed in the environment, nothing about Path and whatever. I don't have python in my path and that works as well, obviously.
– clocktown
Nov 16 at 14:28
I'm seeing the exact same thing (except I'm not using Anaconda)
– David Waterworth
Nov 12 at 9:00
I'm seeing the exact same thing (except I'm not using Anaconda)
– David Waterworth
Nov 12 at 9:00
I've had a similar problem. For me it worked with jupyter, when I enabled the base environment of my anaconda installation.
– alybel
Nov 12 at 10:45
I've had a similar problem. For me it worked with jupyter, when I enabled the base environment of my anaconda installation.
– alybel
Nov 12 at 10:45
Check that jupyter.exe is on your path - see my answer to a similar question here - stackoverflow.com/questions/52287117/…
– David Waterworth
Nov 12 at 21:45
Check that jupyter.exe is on your path - see my answer to a similar question here - stackoverflow.com/questions/52287117/…
– David Waterworth
Nov 12 at 21:45
I have the same problem, and I am using the base environment. Although I can run
jupyter notebook even from inside VS Code in a Python terminal. So it should be working. And adding it to the path completely defeats the purpose of environments, although I haven't tested whether that works. But it states on Microsofts pages that jupyter only needs to be installed in the environment, nothing about Path and whatever. I don't have python in my path and that works as well, obviously.– clocktown
Nov 16 at 14:28
I have the same problem, and I am using the base environment. Although I can run
jupyter notebook even from inside VS Code in a Python terminal. So it should be working. And adding it to the path completely defeats the purpose of environments, although I haven't tested whether that works. But it states on Microsofts pages that jupyter only needs to be installed in the environment, nothing about Path and whatever. I don't have python in my path and that works as well, obviously.– clocktown
Nov 16 at 14:28
add a comment |
1 Answer
1
active
oldest
votes
up vote
2
down vote
accepted
The problem is an issue in the VS Code python extension itself. There are a number of issues related to this open in the repository: #3354, #3343, #3330, and the issues are being worked on, see #3374.
The reason, as far as I understand, is that in this case - and in some other cases - the anaconda environment is not activated before running the command. Situations where the environment is activated are e.g. opening a python terminal or running a file in the python terminal, but this also needs to happen for Jupyter, Tests, and so on.
While theoretically, adding the Scripts folder to your PATH, as David mentioned, could help, it did not help in my case. This may just not be enough to properly reflect what happens on activation.
My guess is that we will have to wait for this issue to be resolved in the repo, but if someone else finds a workaround, I'd be happy.
answered Nov 16 at 15:05
clocktown
13819
Thanks, that makes sense. My configuration is the same as yours, and I agree that it feels wrong to start messing around with the path to address this. I have no doubt I could cobble together something that would work that way, but I'd rather keep my isolation of environments clean and wait for a fix.
– Doug Mahugh
Nov 17 at 18:43
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
accepted
The problem is an issue in the VS Code python extension itself. There are a number of issues related to this open in the repository: #3354, #3343, #3330, and the issues are being worked on, see #3374.
The reason, as far as I understand, is that in this case - and in some other cases - the anaconda environment is not activated before running the command. Situations where the environment is activated are e.g. opening a python terminal or running a file in the python terminal, but this also needs to happen for Jupyter, Tests, and so on.
While theoretically, adding the Scripts folder to your PATH, as David mentioned, could help, it did not help in my case. This may just not be enough to properly reflect what happens on activation.
My guess is that we will have to wait for this issue to be resolved in the repo, but if someone else finds a workaround, I'd be happy.
answered Nov 16 at 15:05
clocktown
13819
Thanks, that makes sense. My configuration is the same as yours, and I agree that it feels wrong to start messing around with the path to address this. I have no doubt I could cobble together something that would work that way, but I'd rather keep my isolation of environments clean and wait for a fix.
– Doug Mahugh
Nov 17 at 18:43
add a comment |
up vote
2
down vote
accepted
The problem is an issue in the VS Code python extension itself. There are a number of issues related to this open in the repository: #3354, #3343, #3330, and the issues are being worked on, see #3374.
The reason, as far as I understand, is that in this case - and in some other cases - the anaconda environment is not activated before running the command. Situations where the environment is activated are e.g. opening a python terminal or running a file in the python terminal, but this also needs to happen for Jupyter, Tests, and so on.
While theoretically, adding the Scripts folder to your PATH, as David mentioned, could help, it did not help in my case. This may just not be enough to properly reflect what happens on activation.
My guess is that we will have to wait for this issue to be resolved in the repo, but if someone else finds a workaround, I'd be happy.
answered Nov 16 at 15:05
clocktown
13819
Thanks, that makes sense. My configuration is the same as yours, and I agree that it feels wrong to start messing around with the path to address this. I have no doubt I could cobble together something that would work that way, but I'd rather keep my isolation of environments clean and wait for a fix.
– Doug Mahugh
Nov 17 at 18:43
add a comment |
up vote
2
down vote
accepted
up vote
2
down vote
accepted
The problem is an issue in the VS Code python extension itself. There are a number of issues related to this open in the repository: #3354, #3343, #3330, and the issues are being worked on, see #3374.
The reason, as far as I understand, is that in this case - and in some other cases - the anaconda environment is not activated before running the command. Situations where the environment is activated are e.g. opening a python terminal or running a file in the python terminal, but this also needs to happen for Jupyter, Tests, and so on.
While theoretically, adding the Scripts folder to your PATH, as David mentioned, could help, it did not help in my case. This may just not be enough to properly reflect what happens on activation.
My guess is that we will have to wait for this issue to be resolved in the repo, but if someone else finds a workaround, I'd be happy.
answered Nov 16 at 15:05
clocktown
13819
The problem is an issue in the VS Code python extension itself. There are a number of issues related to this open in the repository: #3354, #3343, #3330, and the issues are being worked on, see #3374.
The reason, as far as I understand, is that in this case - and in some other cases - the anaconda environment is not activated before running the command. Situations where the environment is activated are e.g. opening a python terminal or running a file in the python terminal, but this also needs to happen for Jupyter, Tests, and so on.
While theoretically, adding the Scripts folder to your PATH, as David mentioned, could help, it did not help in my case. This may just not be enough to properly reflect what happens on activation.
My guess is that we will have to wait for this issue to be resolved in the repo, but if someone else finds a workaround, I'd be happy.
answered Nov 16 at 15:05
clocktown
13819
answered Nov 16 at 15:05
clocktown
13819
answered Nov 16 at 15:05
clocktown
13819
answered Nov 16 at 15:05
clocktown
13819
13819
Thanks, that makes sense. My configuration is the same as yours, and I agree that it feels wrong to start messing around with the path to address this. I have no doubt I could cobble together something that would work that way, but I'd rather keep my isolation of environments clean and wait for a fix.
– Doug Mahugh
Nov 17 at 18:43
add a comment |
Thanks, that makes sense. My configuration is the same as yours, and I agree that it feels wrong to start messing around with the path to address this. I have no doubt I could cobble together something that would work that way, but I'd rather keep my isolation of environments clean and wait for a fix.
– Doug Mahugh
Nov 17 at 18:43
Thanks, that makes sense. My configuration is the same as yours, and I agree that it feels wrong to start messing around with the path to address this. I have no doubt I could cobble together something that would work that way, but I'd rather keep my isolation of environments clean and wait for a fix.
– Doug Mahugh
Nov 17 at 18:43
Thanks, that makes sense. My configuration is the same as yours, and I agree that it feels wrong to start messing around with the path to address this. I have no doubt I could cobble together something that would work that way, but I'd rather keep my isolation of environments clean and wait for a fix.
– Doug Mahugh
Nov 17 at 18:43
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53244986%2frunning-cells-requires-jupyter-notebooks-to-be-installed-error-in-vs-code%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
I'm seeing the exact same thing (except I'm not using Anaconda)
– David Waterworth
Nov 12 at 9:00
I've had a similar problem. For me it worked with jupyter, when I enabled the base environment of my anaconda installation.
– alybel
Nov 12 at 10:45
Check that jupyter.exe is on your path - see my answer to a similar question here - stackoverflow.com/questions/52287117/…
– David Waterworth
Nov 12 at 21:45
I have the same problem, and I am using the base environment. Although I can run
jupyter notebookeven from inside VS Code in a Python terminal. So it should be working. And adding it to the path completely defeats the purpose of environments, although I haven't tested whether that works. But it states on Microsofts pages that jupyter only needs to be installed in the environment, nothing about Path and whatever. I don't have python in my path and that works as well, obviously.– clocktown
Nov 16 at 14:28