[issue17971] Weird interaction between Komodo Python debugger C module & Python 3

Benjamin Peterson added the comment: If you ever find a Python bug, feel free to reopen. -- resolution: -> invalid status: open -> closed ___ Python tracker ___

[issue17971] Weird interaction between Komodo Python debugger C module & Python 3

Eric Promislow added the comment: I found a workaround in our debugger code, so you can lower the priority on this, or even mark it "Wontfix", although I still think the frame stack is getting messed up. One thing about our debugger, it essentially runs all the Python code in a big exec statem

[issue17971] Weird interaction between Komodo Python debugger C module & Python 3

Eric Promislow added the comment: I'm running it inside gdb to see if I can figure it out. I don't see a way of isolating this from the whole product. -- ___ Python tracker ___

[issue17971] Weird interaction between Komodo Python debugger C module & Python 3

Benjamin Peterson added the comment: Since this seems to be some sort of interaction between Komodo's code and Python (it works for me with vanilla Python 3), it's going to be hard to debug without seeing what this other thing is doing. -- nosy: +benjamin.peterson

[issue17971] Weird interaction between Komodo Python debugger C module & Python 3

Changes by Antoine Pitrou : -- nosy: +georg.brandl, ncoghlan ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: ht

[issue17971] Weird interaction between Komodo Python debugger C module & Python 3

New submission from Eric Promislow: While much of Komodo's source code has been released under MIT/GPL/LGPL, the Python debugger hasn't, so I can't post it here. We can work out an arrangement later, although it might not be necessary once I describe the problem: Komodo's Python debugger was