python / python/cpython

int/float specializations should mutate the LHS in-place when possible

Open
#90,530 2 comments 0 reactions 1 assignee View on GitHub

@brandtbucher is already working on this.

Since Jan 14, 2022.

interpreter-core performance type-feature
Dominant language
Python
Stars
77.2k
Forks
36k
PR merge metrics
PR metrics pending

Description

BPO 46372
Nosy @gvanrossum, @mdickinson, @markshannon, @brandtbucher
PRs
  • python/cpython#30594
  • 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/brandtbucher'
    closed_at = None
    created_at = <Date 2022-01-14.06:42:28.312>
    labels = ['interpreter-core', '3.11', 'performance']
    title = 'int/float specializations should mutate the LHS in-place when possible'
    updated_at = <Date 2022-01-31.18:57:11.093>
    user = 'https://github.com/brandtbucher'
    

    bugs.python.org fields:

    activity = <Date 2022-01-31.18:57:11.093>
    actor = 'gvanrossum'
    assignee = 'brandtbucher'
    closed = False
    closed_date = None
    closer = None
    components = ['Interpreter Core']
    creation = <Date 2022-01-14.06:42:28.312>
    creator = 'brandtbucher'
    dependencies = []
    files = []
    hgrepos = []
    issue_num = 46372
    keywords = ['patch']
    message_count = 2.0
    messages = ['410544', '412215']
    nosy_count = 4.0
    nosy_names = ['gvanrossum', 'mark.dickinson', 'Mark.Shannon', 'brandtbucher']
    pr_nums = ['30594']
    priority = 'normal'
    resolution = None
    stage = 'patch review'
    status = 'open'
    superseder = None
    type = 'performance'
    url = 'https://bugs.python.org/issue46372'
    versions = ['Python 3.11']
    

    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.

    Assessment

    This issue has not been assessed yet.

    Get new issues in your inbox

    A short digest of beginner-friendly GitHub issues.