The global config should not be stored on each interpreter

Open
#91,120 9 comments 0 reactions 1 assignee View on GitHub

@ericsnowcurrently is already working on this.

Since Mar 8, 2022.

Assessment

This issue has not been assessed yet.

Description

3.12 interpreter-core topic-C-API
BPO 46964
Nosy @ncoghlan, @vstinner, @ericsnowcurrently
PRs
  • python/cpython#31771
  • 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/ericsnowcurrently'
    closed_at = None
    created_at = <Date 2022-03-08.19:55:53.355>
    labels = ['interpreter-core', 'expert-C-API', '3.11']
    title = 'The global config should not be stored on each interpreter'
    updated_at = <Date 2022-03-30.15:26:47.339>
    user = 'https://github.com/ericsnowcurrently'
    

    bugs.python.org fields:

    activity = <Date 2022-03-30.15:26:47.339>
    actor = 'vstinner'
    assignee = 'eric.snow'
    closed = False
    closed_date = None
    closer = None
    components = ['Interpreter Core', 'C API']
    creation = <Date 2022-03-08.19:55:53.355>
    creator = 'eric.snow'
    dependencies = []
    files = []
    hgrepos = []
    issue_num = 46964
    keywords = ['patch']
    message_count = 8.0
    messages = ['414772', '414789', '415845', '415891', '416061', '416076', '416366', '416373']
    nosy_count = 3.0
    nosy_names = ['ncoghlan', 'vstinner', 'eric.snow']
    pr_nums = ['31771']
    priority = 'normal'
    resolution = None
    stage = 'patch review'
    status = 'open'
    superseder = None
    type = None
    url = 'https://bugs.python.org/issue46964'
    versions = ['Python 3.11']
    

    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.