PyType_Ready doesn't ensure that all bases are ready
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 35/100
Línea de trabajo
Start at the PyType_Ready entry point in CPython's interpreter core and review the issue's historical discussion for the intended behavior. Determine how readiness of base types should be handled, then identify or add focused interpreter-core coverage showing that all bases are ready when PyType_Ready completes.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
| BPO | 3453 |
|---|---|
| Nosy | @ronaldoussoren, @amauryfa, @abalkin, @benjaminp |
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 2008-07-27.15:14:04.037>
labels = ['interpreter-core', 'type-feature']
title = "PyType_Ready doesn't ensure that all bases are ready"
updated_at = <Date 2014-10-29.07:58:15.406>
user = 'https://bugs.python.org/rupole'
bugs.python.org fields:
activity = <Date 2014-10-29.07:58:15.406>
actor = 'pitrou'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2008-07-27.15:14:04.037>
creator = 'rupole'
dependencies = []
files = []
hgrepos = []
issue_num = 3453
keywords = []
message_count = 9.0
messages = ['70322', '70324', '70376', '70378', '70380', '71482', '107502', '193636', '230189']
nosy_count = 6.0
nosy_names = ['ronaldoussoren', 'amaury.forgeotdarc', 'belopolsky', 'rupole', 'benjamin.peterson', 'abusalimov']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue3453'
versions = ['Python 3.5']
- 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
-
🐛 Bug 🔔 Pending processing
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
jumpserver/jumpserver#17584 ·
-
link-check link-check:sphinx-theme
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 90/100
modelscope/DiffSynth-Studio#1702 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
qgis/QGIS-Documentation#11275 ·
-
bug priority:normal ready-for-dev
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
OpenHands/extensions#626 · 1 comentario ·