-
-
Notifications
You must be signed in to change notification settings - Fork 368
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
python 3.11 debugpy error messages #1198
Comments
Thank you for opening this issue! This was previously reported a few times on Jupyter Discourse and it is really confusing for users (who sometimes mis-attribute other issues to this warning as it is common and easy to blame). In particular there is some relevant discussion in https://discourse.jupyter.org/t/debugger-warning-it-seems-that-frozen-modules-are-being-used-python-3-11-0/16544
ipykernel imports debugpy to check if it is available; this is hard to check without import, because the import can error out even if debugpy is installed see #986. I previously suggested always appending |
Seems like a better default, but maybe have some way to opt-out in case it does break someone's workflow? |
Yes, it looks that we could add this in the default kernelspec and make it configurable by having an argument for kernelspec installation app. If it breaks anything we can quickly revert and switch the default. We should condition adding this argument on ipykernel being run in CPython rather than any other Python implementation which might not support this argument. |
Hi,
Using python 3.11 we see the following error:
This comes form
ipykernel/ipykernel/debugger.py
Line 24 in 93a63fb
This was also posted on stackoverflow here: https://stackoverflow.com/questions/75114841/debugger-warning-from-ipython-frozen-modules
Can we fix ipykernel to only show this message when it's applicable (i.e. when trying to debug)?
The text was updated successfully, but these errors were encountered: