This is in a new, clean build using Ubuntu 22.04 LTS and Python 3.11.0 built from source. A new message is appearing when JupyterLab starts: 0.00s - Debugger warning: It seems that frozen modules are being used, which may 0.00s - make the debugger miss breakpoints. Please pass -Xfrozen_modules=off…

I’d wait to make any big decisions… 3.11 wheels for all platforms will be… a while, though. A near term will be reproducible binder environments working with 3.11, and the quickest path to a deeper look at this will likely be via the conda-forge python311 migration … looks like pycurl is the only th…

As of an hour ago or so, binders with an environment.yml specifyng python >=3.11 now seem to work. If you can work up a concrete gist that busts the debugger with frozen modules, we can get down to business.

I’m just getting started with Jupyter (jupyter-lab) and am getting this warning on a freshly installed virtualenv with python3.11 in Dec 2022. Is there any new info about fixing or suppressing this error? I figured out that starting with python -Xfrozen_modules=off -m jupyterlab_server instead of…

Any news on this? I still get the message described above when I try to register a virtual environment in jupyer lab with: python -m ipykernel install --user --name=vpanel I use python 3.11.2

As before: has this warning actually done anything to impact your experience yet?

Well, it has forced me to move back to python 3.10.10…

Does the kernel not start? Did you try setting the environment variable?

Hello! I am having the warnings as well in a similar setup. No impact on the experience except that it tends to pollute logs. For example, when running Jupyter-Book to build an html book from a collection of notebooks, the warning appears once per notebook when it is executed. It makes it harder…

I think the issue is that this warning creates uncertainty about how to proceed without a clear explanation of the warning’s context. Here’s a few questions I imagine could come up when reading this warning: What are frozen modules? What causes the problem with frozen modules and debugger breakpo…

Appending one or more documentation links to this warning with further context might be helpful. This is a fine suggestion but may be easier to act on if filled as an issue against GitHub - microsoft/debugpy: An implementation of the Debug Adapter Protocol for Python which is where the code gener…

Debugger warning: It seems that frozen modules are being used (Python 3.11.0)

JupyterLab

DreamLand7707 July 31, 2023, 11:01am 13

Thanks
But I think that all we need to do is how to pass -Xfrozen_modules=off to python in jupyter.

What should I do about frozen modules warning?

Topic		Replies	Views
What should I do about frozen modules warning? JupyterLab help-wanted	10	17291	March 30, 2024
Debugger warning pass -Xfrozen_modules=off Notebook how-to , help-wanted	0	1789	January 20, 2023
Debugger warning: It seems that frozen modules are being used Notebook notebook	1	1521	February 18, 2024
Debugger warning Notebook how-to , help-wanted	1	4988	February 22, 2023
Missing Debugger Option JupyterLab	17	6059	November 20, 2023

Debugger warning: It seems that frozen modules are being used (Python 3.11.0)

Related topics