Hi, I built cpython on a mac OSX 12.01. Python runs well. When starts, Python shows that version info which looks good: 'Python 3.11.0a5+ (heads/fix-issue-43352:f899da7fe5, Feb 25 2022, 10:04:53) [Clang 13.0.0 (clang-1300.0.29.30)] on darwin' But when I want to used it in VSCode to debug a script, I have the following message: ------- This version of python seems to be incorrectly compiled (internal generated filenames are not absolute). This may make the debugger miss breakpoints. Related bug: http://bugs.python.org/issue1666807 ------- What do I miss ? I looked for a specific option in ./configure but seen nothing ? Can someone help me please ? Thank Yves
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 extension used by VS Code doesn't yet work well with the changes in 3.11 internals. 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 -- I wouldn't blame them if they decided to wait until 3.11 beta 1 is released, which should happen on or after May 6th this year. On Tue, Mar 1, 2022 at 8:25 AM Yves Duprat <yduprat@gmail.com> wrote:
Hi,
I built cpython on a mac OSX 12.01. Python runs well. When starts, Python shows that version info which looks good: 'Python 3.11.0a5+ (heads/fix-issue-43352:f899da7fe5, Feb 25 2022, 10:04:53) [Clang 13.0.0 (clang-1300.0.29.30)] on darwin'
But when I want to used it in VSCode to debug a script, I have the following message: ------- This version of python seems to be incorrectly compiled (internal generated filenames are not absolute). This may make the debugger miss breakpoints. Related bug: http://bugs.python.org/issue1666807 ------- What do I miss ? I looked for a specific option in ./configure but seen nothing ? Can someone help me please ? Thank
Yves _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-leave@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/DISAPV26... Code of Conduct: http://python.org/psf/codeofconduct/
-- --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-c...>
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 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.
On Wed, Mar 2, 2022 at 8:34 AM Yves Duprat <yduprat@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-c...>
Guido van Rossum 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 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
On Wed, Mar 2, 2022 at 8:34 AM Yves Duprat yduprat@gmail.com wrote: 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. there if something's not clear. Ok
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. see: https://github.com/fabioz/PyDev.Debugger/issues/213 see: https://github.com/microsoft/debugpy/issues/861 Thank for your help
participants (2)
-
Guido van Rossum -
Yves Duprat