make function __closure__ writable

Open
#58,577 14 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
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
compilers

Research direction

Start by reviewing the linked PR gh-104946 and the listed writable_closure.patch revisions, then read the issue discussion in the Interpreter Core context. Done means the proposed behavior for making function closure writable is agreed, implemented, and covered by appropriate CPython tests.

Written by the indexing model from the issue text.

Description

3.15 interpreter-core triaged type-feature
BPO 14369
Nosy @rhettinger, @ncoghlan, @pitrou, @benjaminp, @asvetlov, @meadori, @ericsnowcurrently, @akvadrako
Files
  • writable_closure.patch
  • writable_closure_02.patch
  • writable_closure_03.patch
  • writable_closure_04.patch
  • writable_closure_with_checking.patch
    		•

    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 2012-03-19.17:51:16.433>
labels = ['interpreter-core', 'type-feature', '3.7']
title = 'make function __closure__ writable'
updated_at = <Date 2022-03-28.16:35:30.895>
user = 'https://bugs.python.org/YurySelivanov'

    bugs.python.org fields:

    activity = <Date 2022-03-28.16:35:30.895>
actor = 'vstinner'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2012-03-19.17:51:16.433>
creator = 'Yury.Selivanov'
dependencies = []
files = ['24946', '24947', '24962', '24975', '25363']
hgrepos = []
issue_num = 14369
keywords = ['patch']
message_count = 14.0
messages = ['156350', '156357', '156404', '156412', '156452', '159117', '159182', '159235', '159238', '159287', '159519', '304056', '304106', '304199']
nosy_count = 10.0
nosy_names = ['rhettinger', 'ncoghlan', 'pitrou', 'benjamin.peterson', 'asvetlov', 'meador.inge', 'Yury.Selivanov', 'sbt', 'eric.snow', 'akvadrako']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue14369'
versions = ['Python 3.7']

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