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

[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 accidentally got fixed (and then 
investigate how it can be fixed in 3.9).

In my judgement it's not worth anyone (core devs or contributors) spending any 
more time on this (even just reading it and moving on). We have over 7000 open 
issues and only a handful of volunteers reviewing and fixing them.

I found msg412785 a bit rude, but I will give you the benefit of the doubt that 
you didn't intend for it to come across that way. If you still believe that I 
am overstepping my authority and this should be decided by the RMs, I suggest 
you raise this with the SC or on python-dev.

--
resolution:  -> out of date
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[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: closed -> open
versions: +Python 3.9 -Python 3.7

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[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 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[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 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[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 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[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: +iritkatriel
resolution:  -> out of date
stage:  -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[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.

Nevertheless:

$ pdb3.7 ./debug_bug.py 
> /...play/debug_bug.py(1)()
-> a = None
(Pdb) list
  1  -> a = None
  2  
  3  
  4 def fun():
  5 b = False
  6 if a is None:
  7 b = True
  8 pass
  9 else:
 10 pass
 11  
(Pdb) 
 12  
 13 fun()
 14 pass
[EOF]
(Pdb) b 10
Breakpoint 1 at /...play/debug_bug.py:10
(Pdb) run
Restarting ./debug_bug.py with arguments:
./debug_bug.py
> /...play/debug_bug.py(1)()
-> a = None
(Pdb) continue
> /...play/debug_bug.py(10)fun()
-> pass
(Pdb) bt
  /usr/lib/python3.7/bdb.py(585)run()
-> exec(cmd, globals, locals)
  (1)()
  /...play/debug_bug.py(13)()
-> fun()
> /...play/debug_bug.py(10)fun()
-> pass
(Pdb) p b
True
(Pdb)

--
components: Interpreter Core, Library (Lib)
files: debug_bug.py
messages: 382351
nosy: gatekeeper.mail
priority: normal
severity: normal
status: open
title: debugger stops at breakpoint of `pass` that is not actually reached
type: behavior
versions: Python 3.7
Added file: https://bugs.python.org/file49649/debug_bug.py

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com