[issue42548] debugger stops at breakpoint of `pass` that is not actually reached

2022-03-13 Thread Irit Katriel
Irit Katriel added the comment: On second thought I won't keep this open till it expires. This is a low priority bug which no longer exists in new versions because it was fixed by accident due to another change. I don't believe anyone would care enough about this to investigate how it

[issue42548] debugger stops at breakpoint of `pass` that is not actually reached

2022-02-07 Thread Irit Katriel
Irit Katriel added the comment: Fine, I’ll reopen it for 3.9. However, realistically the release managers are unlikely to investigate how this bug got fixed between 3.9 and 3.11 so if you think this is important you might want to do that work. -- resolution: out of date -> status:

[issue42548] debugger stops at breakpoint of `pass` that is not actually reached

2022-02-07 Thread Andy S
Andy S added the comment: Then maybe those RMs (for 3.9 and 3.10) should decide on their own? That should mean the bug should be reopened for them to get assigned to. -- ___ Python tracker

[issue42548] debugger stops at breakpoint of `pass` that is not actually reached

2022-02-07 Thread Irit Katriel
Irit Katriel added the comment: It depends how risky the 3.9 release manager would consider the fix to be. The first step would be to find out which commit(s) fixed it. -- ___ Python tracker

[issue42548] debugger stops at breakpoint of `pass` that is not actually reached

2022-02-07 Thread Andy S
Andy S added the comment: Can reproduce this on 3.9. Is the fact 3.9 is in `bugfix` status enough to backport any fixing changes from 3.11 (if that's true and the bug was fixed)? -- ___ Python tracker

[issue42548] debugger stops at breakpoint of `pass` that is not actually reached

2022-01-15 Thread Irit Katriel
Irit Katriel added the comment: I can't reproduce this on 3.11. 3.7 is no longer maintained, and there have been many changes since then to the trace output. It is likely that this bug has been fixed, but please create a new issue if you see it on a current version. -- nosy:

[issue42548] debugger stops at breakpoint of `pass` that is not actually reached

2020-12-02 Thread Andy S
New submission from Andy S : The python (3.6) doc states (https://docs.python.org/3/reference/simple_stmts.html#the-pass-statement): pass is a null operation... So since this is still an operation one could expect that it can be used as an op to breakpoint on while debugging some scripts.