[issue44621] Python 3.9 traces async for/else incorrectly

Change by Łukasz Langa : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___ ___

[issue44621] Python 3.9 traces async for/else incorrectly

Mark Shannon added the comment: Not quite trivial, but simple enough :) -- ___ Python tracker ___ ___ Python-bugs-list mailing

[issue44621] Python 3.9 traces async for/else incorrectly

Change by Mark Shannon : -- keywords: +patch pull_requests: +25800 stage: -> patch review pull_request: https://github.com/python/cpython/pull/27255 ___ Python tracker ___

[issue44621] Python 3.9 traces async for/else incorrectly

Mark Shannon added the comment: We can fix this for 3.9. The fix to 3.10 was trivial and should port easily. -- ___ Python tracker ___

[issue44621] Python 3.9 traces async for/else incorrectly

Ned Batchelder added the comment: @lukasz.langa, I guess this 3.9 tracing bug should also be closed as wont-fix? -- ___ Python tracker ___

[issue44621] Python 3.9 traces async for/else incorrectly

Ned Batchelder added the comment: The corresponding coverage.py issue: https://github.com/nedbat/coveragepy/issues/1158 -- ___ Python tracker ___

[issue44621] Python 3.9 traces async for/else incorrectly

New submission from Ned Batchelder : Python 3.9 traces this code incorrectly. Note: 3.8 and 3.10 are correct, only 3.9 gets it wrong. --- import linecache, sys def trace(frame, event, arg): # The weird globals here is to avoid a NameError on shutdown...