“Running cells requires Jupyter notebooks to be installed” error in VS Code











up vote
3
down vote

favorite
3












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 Cells tooltips above #%% comments.

  • I've used the Python: Select Interpreter command 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 notebook command 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







share|improve this question






















  • 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 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

















up vote
3
down vote

favorite
3












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 Cells tooltips above #%% comments.

  • I've used the Python: Select Interpreter command 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 notebook command 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







share|improve this question






















  • 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 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















up vote
3
down vote

favorite
3









up vote
3
down vote

favorite
3






3





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 Cells tooltips above #%% comments.

  • I've used the Python: Select Interpreter command 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 notebook command 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







share|improve this question













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 Cells tooltips above #%% comments.

  • I've used the Python: Select Interpreter command 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 notebook command 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






share|improve this question













share|improve this question











share|improve this question




share|improve this question










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 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'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 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'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














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.






share|improve this answer





















  • 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











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















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

























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.






share|improve this answer





















  • 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















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.






share|improve this answer





















  • 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













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.






share|improve this answer












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.







share|improve this answer












share|improve this answer



share|improve this answer










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


















  • 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


















draft saved

draft discarded




















































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.




draft saved


draft discarded














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





















































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







-

Popular posts from this blog

Florida Star v. B. J. F.

Image
Florida Star v. B. J. F. From Wikipedia, the free encyclopedia Jump to navigation Jump to search United States Supreme Court case Florida Star v. B. J. F. Supreme Court of the United States Argued March 21, 1989 Decided June 21, 1989 Full case name The Florida Star v. B. J. F. Citations 491 U.S. 524 ( more ) 109 S. Ct. 2603; 105 L. Ed. 2d 443; 1989 U.S. LEXIS 3120; 57 U.S.L.W. 4816; 16 Media L. Rep. 1801 Prior history The Florida Star v. B.J.F., 530 So.2d 286 (1988) Supreme Court of Florida; Florida Star v. B.J.F., 499 So.2d 883 (1986) Fla. Dist. Court of Appeals Holding Florida Stat. § 794.03 is unconstitutional to the extent it makes the truthful reporting of information that was a matter of public record unlawful, as it violates the First Amendment. Court membership Chief Justice William Rehnquist Associate Justices William J. Brennan Jr.  · Byron White Thurgood Marshall  · Harry Blac...
Read more

Danny Elfman

Image
Danny Elfman From Wikipedia, the free encyclopedia Jump to navigation Jump to search Danny Elfman Elfman at the 2010 San Diego Comic-Con Born Daniel Robert Elfman ( 1953-05-29 ) May 29, 1953 (age 65) Los Angeles, California, U.S. Spouse(s) Bridget Fonda ( m.  2003) Children 1 Musical career Genres Rock [1] ska [2] new wave film music video game music Occupation(s) Composer, singer, songwriter, record producer Instruments Trombone guitar percussion vocals keyboards [3] Years active 1972–present Associated acts Oingo Boingo James Newton Howard Daniel Robert Elfman (born May 29, 1953) is an American composer, singer, songwriter, and record producer. Elfman first became known for being the lead singer and songwriter for the band Oingo Boingo from 1974 to 1995. He is well known for scoring films and television shows, particularly his frequent collabora...
Read more

Lugert, Oklahoma

Image
Unincorporated community in Oklahoma, United States Lugert, Oklahoma Unincorporated community Foundations from the town of Lugert at the bottom of Lake Altus-Lugert Lugert, Oklahoma Location within the state of Oklahoma Coordinates: 34°53′45″N 99°16′31″W  /  34.89583°N 99.27528°W  / 34.89583; -99.27528 Coordinates: 34°53′45″N 99°16′31″W  /  34.89583°N 99.27528°W  / 34.89583; -99.27528 Country United States State Oklahoma County Kiowa Time zone UTC-6 (Central (CST))  • Summer (DST) UTC-5 (CDT) GNIS feature ID 1100597 Lugert is an unincorporated community in Kiowa County, Oklahoma. [1] The town of Lugert was founded in 1901 on 80 acres (320,000 m 2 ). In the town, there was a general store that housed the Post office and sold dry goods, school supplies, groceries, harnesses, axes and much more. It was named for Frank Lugert, who had moved to the area in 1898. Lugert owned land where the town was sited and also owned the general st...
Read more