Document whether it's safe to use bytes for struct format string

Abierto
#60,553 13 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
35/100
Tipo de issue
Documentación
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
python
Área
documentation

Línea de trabajo

Start by reviewing the linked format-bytes.patch and dependency bpo-21071 to understand the bytes-versus-string behavior of struct.Struct.format. Locate the relevant struct documentation and confirm the intended safety guidance; done means the docs clearly state whether using bytes is supported and under what conditions.

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

Descripción

extension-modules
BPO 16349
Nosy @rhettinger, @terryjreedy, @mdickinson, @tiran, @meadori, @takluyver, @vadmium, @serhiy-storchaka
Dependencies
  • bpo-21071: struct.Struct.format is bytes, but should be str
    		•
    Files
  • format-bytes.patch
    		•

    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 2012-10-28.12:43:42.567>
labels = ['extension-modules']
title = "Document whether it's safe to use bytes for struct format string"
updated_at = <Date 2017-04-29.02:46:51.063>
user = 'https://github.com/takluyver'

    bugs.python.org fields:

    activity = <Date 2017-04-29.02:46:51.063>
actor = 'martin.panter'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Extension Modules']
creation = <Date 2012-10-28.12:43:42.567>
creator = 'takluyver'
dependencies = ['21071']
files = ['37489']
hgrepos = []
issue_num = 16349
keywords = ['patch']
message_count = 13.0
messages = ['174042', '174083', '174584', '174680', '174682', '174711', '176681', '176701', '176702', '216656', '232767', '232858', '292554']
nosy_count = 9.0
nosy_names = ['rhettinger', 'terry.reedy', 'mark.dickinson', 'christian.heimes', 'Arfrever', 'meador.inge', 'takluyver', 'martin.panter', 'serhiy.storchaka']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue16349'
versions = ['Python 3.2', 'Python 3.3', '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

    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.