Invalid MIME encoding generated by email.mime (line too long)
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 25/100
Línea de trabajo
Start by reviewing PR 30980 and the linked test_mime_long_line.py and test_mime_long_line_workaround.py files, then inspect the Python email library code they exercise. Reproduce the invalid MIME output and determine whether the existing PR resolves the line-length issue; done means the generated encoding is valid without breaking the relevant email tests.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
| BPO | 25948 |
|---|---|
| Nosy | @warsaw, @bitdancer, @180909 |
| PRs | |
| Files |
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-12-25.10:33:43.528>
labels = ['type-bug', 'expert-email', '3.10', '3.11', 'library', '3.9']
title = 'Invalid MIME encoding generated by email.mime (line too long)'
updated_at = <Date 2022-01-28.07:16:40.176>
user = 'https://bugs.python.org/vog'
bugs.python.org fields:
activity = <Date 2022-01-28.07:16:40.176>
actor = 'wangjiahua'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)', 'email']
creation = <Date 2015-12-25.10:33:43.528>
creator = 'vog'
dependencies = []
files = ['41415', '41416']
hgrepos = []
issue_num = 25948
keywords = ['patch']
message_count = 1.0
messages = ['256982']
nosy_count = 4.0
nosy_names = ['barry', 'r.david.murray', 'vog', 'wangjiahua']
pr_nums = ['30980']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue25948'
versions = ['Python 3.9', 'Python 3.10', 'Python 3.11']
- Lenguaje dominante
- Python
- Estrellas
- 77.2k
- Forks
- 36k
- Merge medio
- 1 d 9 h
- PR fusionados (30 d)
- 558
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de python/cpython
-
docs pending
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
-
stdlib type-feature
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
-
stdlib type-feature
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
-
build type-bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
-
stdlib topic-email type-feature
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
Todos los issues de python/cpython
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 86/100
-
🐛 Bug 🔔 Pending processing
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
jumpserver/jumpserver#17584 ·