This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author nedbat
Recipients Mark.Shannon, nedbat
Date 2021-06-03.10:16:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1622715396.94.0.920593820685.issue44298@roundup.psfhosted.org>
In-reply-to
Content
(I'm not sure whether to create other issues for further details)

I'm also seeing a return in a with will trace withexit/return for a plain "return" statement, but return/withexit/return for a return with a value ("return 17").

I would expect that a statement causing an exit from a with block would always be traced before the with-exit.
History
Date User Action Args
2021-06-03 10:16:36nedbatsetrecipients: + nedbat, Mark.Shannon
2021-06-03 10:16:36nedbatsetmessageid: <1622715396.94.0.920593820685.issue44298@roundup.psfhosted.org>
2021-06-03 10:16:36nedbatlinkissue44298 messages
2021-06-03 10:16:36nedbatcreate