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 changed the bytecode significantly in 3.11 (more than we
did in previous versions, though it tends to change in each version) --
that message is at least a decade old.


> > 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 ?
>

No, you could follow the discussions on
https://github.com/faster-cpython/ideas though and ask specific questions
there if something's not clear.


> >You should probably inquire with either the
> > Pydev extension (https://github.com/fabioz/Pydev) or the VS Code team
> about
> > what their plans are for fixing this
> Thank for the solutions.
>

The specific component to  look for is pydevd --
https://github.com/fabioz/PyDev.Debugger/. I recommend filing an issue
there.

-- 
--Guido van Rossum (python.org/~guido)
*Pronouns: he/him **(why is my pronoun here?)*
<http://feministing.com/2015/02/03/how-using-they-as-a-singular-pronoun-can-change-the-world/>
_______________________________________________
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at 
https://mail.python.org/archives/list/python-dev@python.org/message/4YVNO76TJ4EVMKWOQQSUAPG5LOMDHFTL/
Code of Conduct: http://python.org/psf/codeofconduct/

Reply via email to