[issue45812] SystemError when using code.interact

Pablo Galindo Salgado added the comment: In that case don't worry. I prefer that you report potential bugs without waiting if that's ok with you, my comment was just in case you are familiar with compiling from the CPython repo. Thanks for all the help! -- _

[issue45812] SystemError when using code.interact

Andre Roberge added the comment: I am sorry, but I am not set up to work from the main branch and must rely on official releases. In the future, for alpha and beta releases, I will try to wait for the next release, see immediately if I can reproduce bugs that I had noted before, and submit

[issue45812] SystemError when using code.interact

Pablo Galindo Salgado added the comment: You seem to be using commit e2b4e4b (the release commit), but this issue was fixed very likely in https://bugs.python.org/issue45738. Could you confirm that you cannot reproduce this with the latest main branch? In general, I would kindly recommend to

[issue45812] SystemError when using code.interact

Pablo Galindo Salgado added the comment: Same with 3.10: ❯ ./python.exe Python 3.10.0+ (heads/3.10:7c99e434a9, Nov 16 2021, 09:03:07) [Clang 12.0.0 (clang-1200.0.32.29)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> a = 3 \ 4 File "", line 1 a = 3 \

[issue45812] SystemError when using code.interact

Pablo Galindo Salgado added the comment: I cannot reproduce this in the main branch: ❯ ./python.exe Python 3.11.0a2+ (heads/main:9bf2cbc4c4, Nov 16 2021, 08:59:12) [Clang 12.0.0 (clang-1200.0.32.29)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> import co

[issue45812] SystemError when using code.interact

Pablo Galindo Salgado added the comment: What versions does this affect? Only the main branch? -- ___ Python tracker ___ ___ Python

[issue45812] SystemError when using code.interact

New submission from Andre Roberge : In the following, I execute a single invalid statement in the Python interpreter, which gives the correct error message. Afterwards, I repeat this example using code.interact(), generating a different traceback. This issue affects IDLE differently as shown