struct.pack error messages do not indicate which argument was invalid
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 25/100
Línea de trabajo
Start with the struct.pack implementation and inspect the existing linked PRs gh-103657 and gh-132857. Check how invalid arguments are currently reported and whether the relevant tests cover these errors. Done means struct.pack error messages identify which argument was invalid.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
| BPO | 23578 |
|---|---|
| Nosy | @mdickinson, @meadori, @serhiy-storchaka, @mlouielu |
| PRs |
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 2015-03-03.17:03:05.610>
labels = ['easy', 'type-feature', 'library', '3.11']
title = 'struct.pack error messages do not indicate which argument was invalid'
updated_at = <Date 2022-03-24.00:24:53.123>
user = 'https://bugs.python.org/alynn'
bugs.python.org fields:
activity = <Date 2022-03-24.00:24:53.123>
actor = 'iritkatriel'
assignee = 'serhiy.storchaka'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2015-03-03.17:03:05.610>
creator = 'alynn'
dependencies = []
files = []
hgrepos = []
issue_num = 23578
keywords = ['easy (C)']
message_count = 4.0
messages = ['237153', '288565', '288569', '288570']
nosy_count = 5.0
nosy_names = ['mark.dickinson', 'meador.inge', 'serhiy.storchaka', 'alynn', 'louielu']
pr_nums = ['291']
priority = 'low'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue23578'
versions = ['Python 3.11']
Linked PRs
- gh-103657
- gh-132857
- Lenguaje dominante
- Python
- Estrellas
- 77.2k
- Forks
- 36k
- Merge medio
- 1 d 9 h
- PR fusionados (30 d)
- 558
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de python/cpython
-
docs pending
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
-
stdlib type-feature
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
-
stdlib type-feature
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
-
build type-bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
-
stdlib topic-email type-feature
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
Todos los issues de python/cpython
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
PolicyEngine/policyengine-us#9559 ·
-
priority: p3
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
googleapis/librarian#7636 ·
-
from:qa priority:P2 reliability tech-debt
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
spec-kitty/spec-kitty#4874 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100