-
Notifications
You must be signed in to change notification settings - Fork 194
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Running Jupyter Notebooks with Julia Kernel on M1 Mac #2386
Comments
@davidanthoff to be clear, the problem isn't with Julia extension. As a when around for all of this, my suggestion to the user is to install the Julia extension and use it's built in support for notebooks Is it public or still in preview? With the Julia extension, user works not have to use the jupyter extension to run Julia code in notebooks. |
@DonJayamanne we are shipping the notebook stuff in the released extension, but behind a feature flag. We are just waiting to resolve #2256, and then we'll just remove the feature flag and will have the support always-on. |
Ok, and I'm going to close this issue here, given that this is not a problem on our end :) |
@davidanthoff I want to make sure I am completely clear. Right now I am able to create and use Jupyter notebooks with a Julia kernal on both a Mac with an Intel chip and a Mac with an M1 chip. In both cases, I need to make sure that the Julia:Notebook Controller setting is checked. For the Mac with the M1 chip, I also need to install the Python extension; I do not need to do this for the Mac with the Intel chip. When you resolve #2256, what exactly will change? Will users no longer need to set the Julia: Notebook Controller setting? Will users with a Mac with the M1 chip be able to use Jupyter notebooks without needing to install the Python extension? Finally, what is the timeline on resolving this issue and releasing the next version of the Julia extension? Thanks. |
Oh, hi @daler6, didn't even realize who you were for a while :) I'm not entirely sure what you are doing, but if Python shows up in your workflow, then you are not using the notebook controller from our extension, but instead you are going via the Jupyter extension. Our stuff has no dependency on anything Python at all. Once we resolve #2256 we will remove the notebook controller configuration from the extension and just enable the notebook controller always. |
Aha, I see the problem! I do not even need to install the Jupyter extension. That simplifies things a lot. I was able to open and use an existing notebook. However, now I am having trouble figuring out how to open a new, blank notebook. |
The new notebook command is unfortunately only present in the Jupyter extension... There are a number of rough edges around all of this that we're still trying to iron out, will probably still take a little while :) |
OK, I have found a couple of workarounds in any case. QUICK
SLOW
If there is another way, please let me know. By the way, I am going through all this because on Tuesday, I start teaching a class to upper level undergraduates on Data Science with Julia. So, please expect to see other questions coming your way. :) |
I think the other option is to install the Jupyter extension and then there is a command to create a new Jupyter notebook. Very exciting to hear about the course! |
I submitted the following under the vscode-jupyter issue area and was informed that it was a duplicate of issue #5206 there. After a couple of iterations, though, it seems that the problem may be with the Julia extension, so I was asked to resubmit here.
Environment data
VS Code version: 1.59
Jupyter Extension version (available under the Extensions sidebar): 2021.8.1236758218
Python Extension version (available under the Extensions sidebar): 2021.8.1147840270
OS (Windows | Mac | Linux distro) and version: macOS Big Sur 11.5.2
Jupyter server running: Local | Remote | N/A
Julia extension: 1.3.30, with Julia:Notebook Controller option checked
Expected behaviour
When I open an existing or new Jupyter notebook and select the Julia kernel, everything should work fine.
Actual behaviour
I am told that I need to install the Python extension for this to work. Once I install that extension, it does work.
This seems to only happen on my new M1 MacMini. On my MacBookPro with an Intel chip running the same setup, I do not need to install the Python extension to run Jupyter Notebooks.
The text was updated successfully, but these errors were encountered: