You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 26, 2022. It is now read-only.
I read in the documentation that debugging using the ipykernel should now be possible starting jupyterlab version 3.
I have currently installed jupyterlab (3.2.4) and ipykernel (6.5.1) but the debugging toggle is not active.
However, debugging works with the xeus-python kernel.
Reproduce
This is the case in a fresh conda environment.
The text was updated successfully, but these errors were encountered:
Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗
If you haven't done so already, check out Jupyter's Code of Conduct. Also, please try to follow the issue template as it helps other other community members to contribute more effectively.
You can meet the other Jovyans by joining our Discourse forum. There is also an intro thread there where you can stop by and say Hi! 👋
I have seen this caused by the wrong kernelspec getting picked up (also using Anaconda).
If you run jupyter --paths you should see a few directories listed under the data: heading. These are where kernelspecs are searched for.
If you open each directory in order and check the kernel subdirectory for python3, the first one you find should be the one that Jupyter server is finding as well. If the kernel.json inside there doesn't have the metadata.debugger = true key as in the example below, that explains why it isn't enabled in JLab. There are a few ways to resolve this:
Simply add the missing debugger key. However, depending on your setup this may cause problems when switching between Anaconda environments if the targeted ipykernel version doesn't support debugging.
If there is another instance of the python3 kernel directory later on that does have the key, you can rename the first (or second) python3 directory to avoid the collision so that both are accessible. You can also change the display_name to help you determine which is which.
Here's the content of one of my debuggable kernel.json files for reference:
Description
I read in the documentation that debugging using the ipykernel should now be possible starting jupyterlab version 3.
I have currently installed jupyterlab (3.2.4) and ipykernel (6.5.1) but the debugging toggle is not active.
However, debugging works with the xeus-python kernel.
Reproduce
This is the case in a fresh conda environment.
The text was updated successfully, but these errors were encountered: