Nested finally in generators don't follow PEP 342

Open
#43,848 11 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
compilers

Research direction

Start by reading the linked generator_finalization.py file and the issue title in the context of PEP 342. Investigate the Python interpreter's handling of nested finally blocks in generators and determine the expected behavior from the report. Done means the behavior conforms to PEP 342, with coverage for the reported case.

Written by the indexing model from the issue text.

Description

interpreter-core pending
BPO 1542308
Nosy @gvanrossum, @pjeby, @etrepum, @pitrou
Files
  • generator_finalization.py
    		•

    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 = None
closed_at = None
created_at = <Date 2006-08-17.22:56:50.000>
labels = ['interpreter-core']
title = "Nested finally in generators don't follow PEP 342"
updated_at = <Date 2014-03-23.00:57:03.566>
user = 'https://github.com/etrepum'

    bugs.python.org fields:

    activity = <Date 2014-03-23.00:57:03.566>
actor = 'BreamoreBoy'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2006-08-17.22:56:50.000>
creator = 'bob.ippolito'
dependencies = []
files = ['2114']
hgrepos = []
issue_num = 1542308
keywords = []
message_count = 8.0
messages = ['29543', '29544', '29545', '29546', '29547', '29548', '68152', '214530']
nosy_count = 5.0
nosy_names = ['gvanrossum', 'pje', 'bob.ippolito', 'pitrou', 'BreamoreBoy']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'languishing'
superseder = None
type = None
url = 'https://bugs.python.org/issue1542308'
versions = ['Python 2.5']

    Dominant language
    Python
    Stars
    77.2k
    Forks
    36k
    Avg merge
    1d 9h
    Merged PRs (30d)
    558

    Contributor guide

    Open the contributing guide

    First steps

    1. Read the whole issue, then the project's contributing guide.
    2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
    3. Fork the repository and make your change on a branch.
    4. Open a pull request that references the issue number.

    More from python/cpython

    All issues in python/cpython

    Similar issues

    More Python issues

    Get new issues in your inbox

    A short digest of beginner-friendly GitHub issues.