TypeError message incorrect for max() with one keyword arg

Abierto
#60,719 8 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
35/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
python
Área
compilers

Línea de trabajo

Start by reading issue16515.diff and issue16515-unpacktuple.diff, then trace the max() argument-handling path and PyArg_UnpackTuple entry point in CPython. Compare the current TypeError wording with the issue's stated problem and validate the correction against related interpreter behavior. Done means the one-keyword-argument max() case reports the correct message without regressing missing-argument messages.

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

Descripción

interpreter-core type-bug
BPO 16515
Nosy @mdickinson, @ezio-melotti, @cjerdonek
Dependencies
  • bpo-16543: improve TypeError messages for missing arguments (meta issue)
    		•
    Files
  • issue16515.diff: Patch against 3.2.
  • issue16515-unpacktuple.diff: Patch against 3.2 to fix the message in PyArg_UnpackTuple.
    		•

    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 2012-11-20.22:36:57.084>
labels = ['interpreter-core', 'type-bug', '3.8', '3.9', '3.10']
title = 'TypeError message incorrect for max() with one keyword arg'
updated_at = <Date 2020-10-22.18:35:07.206>
user = 'https://github.com/cjerdonek'

    bugs.python.org fields:

    activity = <Date 2020-10-22.18:35:07.206>
actor = 'iritkatriel'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2012-11-20.22:36:57.084>
creator = 'chris.jerdonek'
dependencies = ['16543']
files = ['28064', '28065']
hgrepos = []
issue_num = 16515
keywords = ['patch']
message_count = 7.0
messages = ['176034', '176044', '176063', '176067', '176068', '176070', '176204']
nosy_count = 3.0
nosy_names = ['mark.dickinson', 'ezio.melotti', 'chris.jerdonek']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue16515'
versions = ['Python 3.8', 'Python 3.9', 'Python 3.10']

    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.