Lib/types.py nit: isinstance != PyType_IsSubtype

Abierto
#67,157 7 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
python
Área
backend

Línea de trabajo

Start by reading Lib/types.py and the linked fix_types_calculate_meta patch files, then inspect the referenced virtual-metaclass test patches. Compare the Python implementation with the native type machinery; done means the behavior matches PyType_IsSubtype and the corresponding tests pass.

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

Descripción

stdlib type-bug
BPO 22968
Nosy @1st1
Files
  • fix_types_calculate_meta.patch: More correct implementation of types._caclculate_meta
  • fix_types_calculate_meta_v2.patch: v2: More correct implementation of class creation APIs in Lib/types.py
  • fix_types_calculate_meta_v3.patch: v3: Just adds a commit message
  • test_virtual_metaclasses.patch: Tests verifying that type machinery really works this way
  • test_virtual_metaclasses_in_types_module.patch: Tests verifying that types.py matches type machinery
  • test_virtual_metaclasses_in_types_module_v2.patch: Tests verifying that types.py implementation matches native type machinery
    		•

    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 2014-11-29.20:38:33.991>
labels = ['type-bug', 'library']
title = 'Lib/types.py nit: isinstance != PyType_IsSubtype'
updated_at = <Date 2015-10-24.15:02:13.263>
user = 'https://bugs.python.org/gmt'

    bugs.python.org fields:

    activity = <Date 2015-10-24.15:02:13.263>
actor = 'serhiy.storchaka'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2014-11-29.20:38:33.991>
creator = 'gmt'
dependencies = []
files = ['37318', '37348', '37349', '37350', '37352', '37356']
hgrepos = []
issue_num = 22968
keywords = ['patch']
message_count = 7.0
messages = ['231871', '231980', '232067', '232074', '232075', '232077', '232104']
nosy_count = 2.0
nosy_names = ['yselivanov', 'gmt']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue22968'
versions = ['Python 3.4', 'Python 3.5', 'Python 3.6']

    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.