python / python/cpython

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

Abierto
#72,495 2 comentarios 0 reacciones 1 asignado Ver en GitHub

@serhiy-storchaka ya está trabajando en esto.

Desde el 25/12/2017.

interpreter-core performance type-feature
Lenguaje dominante
Python
Estrellas
77.2k
Forks
36k
Merge medio
1 d 9 h
PR fusionados (30 d)
558

Descripción

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']
    

    Guía de contribución

    Abrir la guía de contribución

    Primeros pasos

    1. Lee el issue completo y luego la guía de contribución del proyecto.
    2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
    3. Haz un fork del repositorio y trabaja en una rama.
    4. Abre un pull request que haga referencia al número del issue.

    Evaluación

    Este issue todavía no se ha evaluado.

    Recibe los nuevos issues en tu correo

    Un resumen breve de issues de GitHub para principiantes.