poplib: Line too long error causes knock-on failure to retrieve all subsequent messages

Abierto
#68,894 1 comentario 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
25/100
Tipo de issue
Error
Claridad
Necesita aclaración
Estado de actividad
Estancado
Stack tecnológico
python
Área
networking

Línea de trabajo

Start by locating the Python poplib implementation and reproducing the line-too-long error described in the title, with attention to how subsequent messages are retrieved. Done means the error no longer prevents retrieval of later messages, with regression coverage for the reported behavior.

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

Descripción

stdlib topic-email
BPO 24706

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-07-24.15:24:32.632>
labels = ['library']
title = 'poplib: Line too long error causes knock-on failure to retrieve all subsequent messages'
updated_at = <Date 2015-07-24.15:24:32.632>
user = 'https://bugs.python.org/ChrisSmowton'

bugs.python.org fields:

activity = <Date 2015-07-24.15:24:32.632>
actor = 'Chris Smowton'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2015-07-24.15:24:32.632>
creator = 'Chris Smowton'
dependencies = []
files = []
hgrepos = []
issue_num = 24706
keywords = []
message_count = 1.0
messages = ['247283']
nosy_count = 1.0
nosy_names = ['Chris Smowton']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue24706'
versions = ['Python 2.7']

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.