implement PEP 3118 struct changes

Abierto
#47,382 63 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
20/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
python
Área
backend

Línea de trabajo

Read the linked pep-3118.patch and struct-string.py3k.3.patch first, then compare their proposed changes with grammar.y. Confirm the remaining PEP 3118 struct work and its required tests before proceeding; done means the agreed changes are implemented and validated.

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

Descripción

stdlib type-feature
BPO 3132
Nosy @warsaw, @mdickinson, @ncoghlan, @abalkin, @pitrou, @devdanzin, @benjaminp, @pv, @skrah, @meadori, @vadmium
Files
  • pep-3118.patch
  • struct-string.py3k.patch: Patch for 'T{}' syntax and multiple byte order specifiers.
  • struct-string.py3k.2.patch: Patch with fixed assertions
  • struct-string.py3k.3.patch: Patch for 'T{}' against py3k r87813
  • grammar.y
    		•

    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-06-17.22:30:31.496>
labels = ['type-feature', 'library']
title = 'implement PEP 3118 struct changes'
updated_at = <Date 2016-04-13.10:20:21.199>
user = 'https://github.com/benjaminp'

    bugs.python.org fields:

    activity = <Date 2016-04-13.10:20:21.199>
actor = 'skrah'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2008-06-17.22:30:31.496>
creator = 'benjamin.peterson'
dependencies = []
files = ['16242', '17386', '17416', '20298', '42451']
hgrepos = []
issue_num = 3132
keywords = ['patch']
message_count = 58.0
messages = ['68347', '68507', '71313', '71316', '71338', '71342', '71882', '87921', '99296', '99297', '99309', '99312', '99313', '99460', '99472', '99474', '99551', '99655', '99656', '99677', '99711', '99771', '105952', '105955', '105970', '106087', '106088', '106089', '106090', '106091', '106153', '106155', '106157', '106164', '106168', '106173', '106175', '106177', '106180', '106181', '106188', '106416', '123093', '123204', '123205', '123226', '123366', '125617', '130694', '130695', '130696', '143505', '143509', '167963', '187583', '187589', '187591', '263321']
nosy_count = 17.0
nosy_names = ['barry', 'teoliphant', 'mark.dickinson', 'ncoghlan', 'belopolsky', 'pitrou', 'inducer', 'ajaksu2', 'MrJean1', 'benjamin.peterson', 'pv', 'Arfrever', 'noufal', 'skrah', 'meador.inge', 'martin.panter', 'paulehoffman']
pr_nums = []
priority = 'high'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue3132'
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.