PEP447: Add type.__getdescriptor__

Abierto
#62,381 27 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
15/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Estancado
Stack tecnológico
python
Área
compilers

Línea de trabajo

Start by reading the latest referenced proposal, pep447-2015-07-26.txt, alongside super-hook-proposal.rst and the earlier issue-18181 patches. The issue is in patch review with no repository entry point or tests named; done would require an agreed implementation of type.getdescriptor, not another proposal revision.

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

Descripción

interpreter-core type-feature
BPO 18181
Nosy @ronaldoussoren, @amauryfa
Files
  • supers_updated.py
  • issue-18181-poc-v4.txt
  • super-hook-proposal.rst
  • issue18181-locallookup-only-super.txt
  • issue-18181-full-v1.txt
  • issue-18181-full-v2.txt
  • issue-18181-full-v2b.txt
  • issue-18181-full-v3.txt
  • issue-18181-full-v4.txt
  • pep447-2015-07-25.txt
  • pep447-micro-bench.py
  • pep447-2015-07-25-v2.txt
  • pep447-2015-07-26.txt
  • pep447-2015-07-26.txt: Updated patch for trunk with minor code cleanup
    		•

    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-06-10.13:15:53.900>
labels = ['interpreter-core', 'type-bug']
title = 'PEP447: Add type.__getdescriptor__'
updated_at = <Date 2016-07-24.07:56:54.166>
user = 'https://github.com/ronaldoussoren'

    bugs.python.org fields:

    activity = <Date 2016-07-24.07:56:54.166>
actor = 'ronaldoussoren'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2013-06-10.13:15:53.900>
creator = 'ronaldoussoren'
dependencies = []
files = ['30547', '30766', '30767', '30928', '30951', '31008', '31014', '31071', '31107', '40012', '40013', '40017', '40027', '43853']
hgrepos = []
issue_num = 18181
keywords = ['patch']
message_count = 27.0
messages = ['190905', '190909', '190912', '190920', '190921', '190965', '190971', '190972', '190976', '190979', '191020', '191021', '192274', '192275', '193100', '193109', '193232', '193538', '193547', '193861', '194038', '247187', '247323', '247330', '247349', '247350', '247419']
nosy_count = 2.0
nosy_names = ['ronaldoussoren', 'amaury.forgeotdarc']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue18181'
versions = ['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.