Incorrect operand precedence when implementing sequences in C

Abierto
#55,686 29 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
25/100
Tipo de issue
Error
Claridad
Necesita aclaración
Estado de actividad
Estancado
Stack tecnológico
c, python
Área
compilers

Línea de trabajo

Start by reviewing the historical patches issue11477_LHS_prededence.diff, 650549138a3d.diff, and 8bd713a823b5.diff, then read the linked issue discussion to identify the affected interpreter-core code. Establish the current C implementation and regression coverage for sequence operand precedence; done means the incorrect precedence is corrected and relevant tests pass.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

3.11 interpreter-core type-bug
BPO 11477
Nosy @rhettinger, @terryjreedy, @gpshead, @ncoghlan, @cfbolz, @benjaminp, @merwok, @alex, @Trundle, @meadori, @durban, @ericsnowcurrently, @serhiy-storchaka, @iritkatriel
Files
  • issue11477_LHS_prededence.diff: Patch generated via rdiff extension
  • 650549138a3d.diff
  • 8bd713a823b5.diff
    		•

    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 2011-03-12.21:24:50.923>
labels = ['interpreter-core', 'type-bug', '3.11']
title = 'Incorrect operand precedence when implementing sequences in C'
updated_at = <Date 2021-10-26.00:55:14.406>
user = 'https://github.com/terryjreedy'

    bugs.python.org fields:

    activity = <Date 2021-10-26.00:55:14.406>
actor = 'gregory.p.smith'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2011-03-12.21:24:50.923>
creator = 'terry.reedy'
dependencies = []
files = ['21219', '21368', '21386']
hgrepos = ['3']
issue_num = 11477
keywords = ['patch']
message_count = 27.0
messages = ['130698', '130728', '130736', '130812', '130866', '130867', '130909', '130925', '130974', '130976', '130994', '131001', '131004', '131007', '131022', '131030', '131057', '131211', '131212', '132052', '158917', '158918', '160138', '179031', '243301', '405003', '405017']
nosy_count = 14.0
nosy_names = ['rhettinger', 'terry.reedy', 'gregory.p.smith', 'ncoghlan', 'Carl.Friedrich.Bolz', 'benjamin.peterson', 'eric.araujo', 'alex', 'Trundle', 'meador.inge', 'daniel.urban', 'eric.snow', 'serhiy.storchaka', 'iritkatriel']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue11477'
versions = ['Python 3.11']

    Lenguaje dominante
    Python
    Estrellas
    77.2k
    Forks
    36k
    Merge medio
    1 d 9 h
    PR fusionados (30 d)
    558

    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.

    Más de python/cpython

    Todos los issues de python/cpython

    Issues similares

    Más issues de Python

    Recibe los nuevos issues en tu correo

    Un resumen breve de issues de GitHub para principiantes.