Closed mlucool closed 9 months ago
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
Can we fix ipykernel to only show this message when it's applicable (i.e. when trying to debug)?
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 https://github.com/ipython/ipykernel/issues/986.
I previously suggested always appending -Xfrozen_modules=off
on a higher level (on ipykernel startup). It is unclear to me if there is any downside to doing that, maybe we should give it a try?
I previously suggested always appending -Xfrozen_modules=off on a higher level (on ipykernel startup). It is unclear to me if there is any downside to doing that, maybe we should give it a try?
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 https://github.com/ipython/ipykernel/blob/93a63fb7b8752899ed95118fa35e56f74eedd0c6/ipykernel/debugger.py#L24.
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)?