Drop restriction that meta.__prepare__() must return a dict (subclass)
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 by reading the linked type-namespace-restriction.diff patch, then review the dependent issues bpo-17422 and bpo-31588 for related constraints and failure cases. Done means the restriction on meta.prepare() is addressed consistently and the relevant class-creation behavior is verified by tests.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
| BPO | 17421 |
|---|---|
| Nosy | @loewis, @ncoghlan, @vstinner, @durban, @ericsnowcurrently, @serhiy-storchaka, @cdonovick |
| Dependencies | |
| Files |
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 2013-03-14.20:20:27.737>
labels = ['type-feature']
title = 'Drop restriction that meta.__prepare__() must return a dict (subclass)'
updated_at = <Date 2019-03-12.22:17:10.507>
user = 'https://github.com/ericsnowcurrently'
bugs.python.org fields:
activity = <Date 2019-03-12.22:17:10.507>
actor = 'donovick'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = []
creation = <Date 2013-03-14.20:20:27.737>
creator = 'eric.snow'
dependencies = ['17422', '31588']
files = ['29408']
hgrepos = []
issue_num = 17421
keywords = ['patch']
message_count = 6.0
messages = ['184187', '184203', '184206', '184309', '303022', '337814']
nosy_count = 7.0
nosy_names = ['loewis', 'ncoghlan', 'vstinner', 'daniel.urban', 'eric.snow', 'serhiy.storchaka', 'donovick']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue17421'
versions = ['Python 3.4']
- 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 1/5 Menos de una hora Aptitud para principiantes 90/100
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 86/100
zostera/django-bootstrap4#894 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
use-agent-os/agent-os#3276 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
zephyrproject-rtos/zephyr#119726 ·
-
area/auth bug comp/agent P3 platform/discord type/security
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
NousResearch/hermes-agent#117848 ·