break/continue or return in finally block occurs twice in trace.

[markshannon]

BPO	42645
Nosy	@nedbat, @markshannon
PRs	bpo-42645: Make sure that return/break/continue are only traced once when exiting via a finally block. #23780

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = 'https://github.com/markshannon'
closed_at = <Date 2020-12-17.13:56:51.132>
created_at = <Date 2020-12-15.12:21:32.578>
labels = ['type-bug', '3.10']
title = 'break/continue or return in finally block occurs twice in trace.'
updated_at = <Date 2020-12-17.13:56:51.131>
user = 'https://github.com/markshannon'

bugs.python.org fields:

activity = <Date 2020-12-17.13:56:51.131>
actor = 'Mark.Shannon'
assignee = 'Mark.Shannon'
closed = True
closed_date = <Date 2020-12-17.13:56:51.132>
closer = 'Mark.Shannon'
components = []
creation = <Date 2020-12-15.12:21:32.578>
creator = 'Mark.Shannon'
dependencies = []
files = []
hgrepos = []
issue_num = 42645
keywords = ['patch']
message_count = 2.0
messages = ['383044', '383165']
nosy_count = 2.0
nosy_names = ['nedbat', 'Mark.Shannon']
pr_nums = ['23780']
priority = 'normal'
resolution = 'fixed'
stage = 'resolved'
status = 'closed'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue42645'
versions = ['Python 3.10']

[markshannon]

This function

def f():
     try:
         return 2
     finally:
         4

would generate a try of [1, 2, 4, 2]. It should generate [1, 2, 4]
and not trace the return twice.

[markshannon]

New changeset 5274b68 by Mark Shannon in branch 'master':
bpo-42645: Make sure that return/break/continue are only traced once when exiting via a finally block. (GH-23780)
5274b68