[issue13548] line number when tracing an implicit return

Irit Katriel added the comment: Yes, you're right. I don't know what I thought I saw before. It works on the mac as well. -- resolution: -> out of date stage: -> resolved status: open -> closed ___ Python tracker

[issue13548] line number when tracing an implicit return

Terry J. Reedy added the comment: The attached badlineevent.py with print updated. -- ___ Python tracker ___ ___ Python-bugs-list m

[issue13548] line number when tracing an implicit return

Irit Katriel added the comment: Terry, I'm pretty sure I saw the problem on the mac earlier. Can you paste the contents of tem.py? -- ___ Python tracker ___ _

[issue13548] line number when tracing an implicit return

Terry J. Reedy added the comment: This seems to be fixed. On 3.11.0a2 installed on Windows and fresh build of .0a2+, I see return on line 11, which is correct. f:\dev\3x>python ../tem/tem.py Running Debug|x64 interpreter... f:\dev\tem\tem.py 7 call f:\dev\tem\tem.py 8 line f:\dev\tem\tem.py

[issue13548] line number when tracing an implicit return

Irit Katriel added the comment: Reproduced on 3.11. An implicit return doesn't have a line, so it's not clear what should happen. Assigning the next line to it wouldn't be correct either (it could be the first line of the next function). We could say that in this case there is no line ev