NameError for built in function open when re-raising stored exception from yielded function

Open
#70,715 10 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
compilers

Research direction

Start with the attached gen_err.py reproduction and the Interpreter Core issue details, then check linked PR gh-120087 for the current work. Confirm the reported NameError when re-raising the stored exception from the yielded function; done means the reproduction no longer produces that error.

Written by the indexing model from the issue text.

Description

interpreter-core type-bug
BPO 26528
Nosy @pitrou, @vstinner, @sorcio, @vadmium, @serhiy-storchaka, @rooterkyberian, @iritkatriel
Files
  • gen_err.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 2016-03-10.12:09:57.654>
labels = ['interpreter-core', 'type-bug', '3.9', '3.10', '3.11']
title = 'NameError for built in function open when re-raising stored exception from yielded function'
updated_at = <Date 2021-12-14.00:10:12.108>
user = 'https://bugs.python.org/reidfaiv'

    bugs.python.org fields:

    activity = <Date 2021-12-14.00:10:12.108>
actor = 'iritkatriel'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2016-03-10.12:09:57.654>
creator = 'reidfaiv'
dependencies = []
files = ['42114']
hgrepos = []
issue_num = 26528
keywords = []
message_count = 10.0
messages = ['261497', '261499', '261500', '261524', '261550', '297950', '309462', '340783', '380026', '408504']
nosy_count = 8.0
nosy_names = ['pitrou', 'vstinner', 'davide.rizzo', 'martin.panter', 'serhiy.storchaka', 'reidfaiv', 'rooter', 'iritkatriel']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue26528'
versions = ['Python 3.9', 'Python 3.10', 'Python 3.11']

    Linked PRs
    • gh-120087
    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.