email parsing docs: clarify that only ASCII strings are supported

Abierto
#69,731 19 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
32/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 reading the issue discussion and the attached email_get_payload__test.py and parse-text.py files to understand the reported behavior. Locate the current email parsing documentation and confirm where string input is described. Done means the relevant documentation clearly states that only ASCII strings are supported, with any existing documentation checks still passing.

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

Descripción

docs stdlib topic-email
BPO 25545
Nosy @warsaw, @jaraco, @bitdancer, @jayvdb
Files
  • email_get_payload__test.py
  • parse-text.py
    		•

    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 2015-11-03.14:43:30.136>
labels = ['type-bug', 'library']
title = 'email parsing docs: clarify that only ASCII strings are supported'
updated_at = <Date 2019-04-26.16:47:53.820>
user = 'https://bugs.python.org/tanzerswingcoat'

    bugs.python.org fields:

    activity = <Date 2019-04-26.16:47:53.820>
actor = 'immerrr again'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2015-11-03.14:43:30.136>
creator = 'tanzer@swing.co.at'
dependencies = []
files = ['40934', '47978']
hgrepos = []
issue_num = 25545
keywords = []
message_count = 19.0
messages = ['253994', '254014', '254041', '254058', '254066', '254067', '254095', '254131', '254179', '254189', '254262', '254315', '254322', '254325', '331159', '331183', '340841', '340931', '340934']
nosy_count = 6.0
nosy_names = ['barry', 'jaraco', 'r.david.murray', 'jayvdb', 'tanzer@swing.co.at', 'immerrr again']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue25545'
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.