Guido van Rossum wrote:
> On Wed, Mar 2, 2022 at 8:34 AM Yves Duprat ydup...@gmail.com wrote:
> > How did you find that issue?
> > This message printed from VSCode when I ran my script in debug mode
> > Oh, I see, this is something that pydevd prints when it doesn't understand
> the .pyc file. We c
On Wed, Mar 2, 2022 at 8:34 AM Yves Duprat wrote:
> > How did you find that issue?
> This message printed from VSCode when I ran my script in debug mode
>
Oh, I see, this is something that pydevd prints when it doesn't understand
the .pyc file. We changed the bytecode significantly in 3.11 (more
> How did you find that issue?
This message printed from VSCode when I ran my script in debug mode
> the Pydev extension used by VS Code doesn't yet work well with
> the changes in 3.11 internals.
Is there a simple sheet, white paper about these internal changes ?
>You should probably inquire w
How did you find that issue? It seems unlikely that a problem with 3.11 is
caused by an issue reported for Python 2.5 in 2007.
My own understanding of the problem with the VS Code debugger and 3.11
(which I have experienced myself as well :-) is that since 3.11 is still in
alpha mode, the Pydev ex
