May be this issue can be reopen ?
microsoft/vscode-python#941

@YvesDup You should create an issue in the corresponding repository - this one is specifically for debugpy, but the issue you've linked to is about the way vscode-python uses debugpy.

A workaround is to add this to the configuation in launch.json:

"pythonArgs": ["-Xfrozen_modules=off"],

@int19h Sorry :( for the misunderstood. I just proposed to add a new entry to pass args to Python like proposed in that issue. But it already exists as the "pythonArgs" of lauch.json.

I am wondering what are the differences debugpy and pydev.debugger ? Are they both a debugger for Python or not or something more ? Thank

PyDev.Debugger aka pydevd is one of the oldest Python debuggers around - it's the one originally made for Eclipse/PyDev, hence the name. It implements core functionality such as stepping and breakpoints. It runs inside the process being debugged, and thus, in general, it does things that are best done from within that process.

debugpy is basically a wrapper around pydevd that adds process lifetime management. It runs as a separate process from the debuggee, and thus, in general, it does things that are best done from outside of the process that is being debugged. So it can handle requests to launch processes for debugging or attach to running processes (and sets up pydevd as needed to handle those scenarios), and it keeps track of and coordinates processes in a multiprocess debug session. But it also does stuff such as stdout/stderr output capture.

To allow for easy deployment, debugpy vendors (i.e. embeds) all of its dependencies outside of the Python stdlib, including pydevd. So you don't have to worry about any of this while using it, but when we track work to be done, it can end up in either repo depending on where it was originally reported, and what the issue is.

@int19h Thank for your explanation

Fixed by #937

not fixed https://github.com/microsoft/debugpy/pull/937/files#r1145404312

Not working with non-fork subprocesses due upstream bug python/cpython#106723

For what it's worth, I just converted from Python 3.9.12 to Python 3.11.4 and had to add export PYDEVD_DISABLE_FILE_VALIDATION=1 && into makefile commands to get rid of the error message. But even with the messages suppressed, it would appear that the compiles are taking a lot longer to complete