python / python/cpython

Accelerate 'string'.format(value, ...) by using formatted string literals

Open
#72,495 2 comments 0 reactions 1 assignee View on GitHub

@serhiy-storchaka is already working on this.

Since Dec 25, 2017.

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

Description

BPO 28308
Nosy @ericvsmith, @serhiy-storchaka, @isidentical
Dependencies
  • bpo-11549: Build-out an AST optimizer, moving some functionality out of the peephole optimizer
  • 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/serhiy-storchaka'
    closed_at = None
    created_at = <Date 2016-09-29.08:50:04.036>
    labels = ['interpreter-core', '3.7', 'performance']
    title = "Accelerate 'string'.format(value, ...) by using formatted string literals"
    updated_at = <Date 2020-02-14.20:42:51.446>
    user = 'https://github.com/serhiy-storchaka'
    

    bugs.python.org fields:

    activity = <Date 2020-02-14.20:42:51.446>
    actor = 'BTaskaya'
    assignee = 'serhiy.storchaka'
    closed = False
    closed_date = None
    closer = None
    components = ['Interpreter Core']
    creation = <Date 2016-09-29.08:50:04.036>
    creator = 'serhiy.storchaka'
    dependencies = ['11549']
    files = []
    hgrepos = []
    issue_num = 28308
    keywords = []
    message_count = 2.0
    messages = ['277689', '277693']
    nosy_count = 3.0
    nosy_names = ['eric.smith', 'serhiy.storchaka', 'BTaskaya']
    pr_nums = []
    priority = 'low'
    resolution = None
    stage = None
    status = 'open'
    superseder = None
    type = 'performance'
    url = 'https://bugs.python.org/issue28308'
    versions = ['Python 3.7']
    

    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.