EmailMessage.add_attachment() creates parts with spurious MIME-Version header.

Abierto
#69,422 12 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
25/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
python
Área
backend

Línea de trabajo

Start with the failing and revised test patches named in the issue, then compare them with fix_mime_version_headers.patch and fix_mime_version_headers-2.patch. Review the email component's attachment behavior and use those tests to verify that add_attachment() no longer adds a spurious MIME-Version header to attachment parts.

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

Descripción

stdlib topic-email type-bug
BPO 25235
Nosy @warsaw, @bitdancer, @eriker-fsc
Files
  • test_add_attachment_does_not_add_MIME_Version_in_attachment.patch: failing test case
  • test_add_attachment_does_not_add_MIME_Version_in_attachment.patch: revised failing tests
  • test_MIME_Version.patch: Actually revised patch.
  • fix_mime_version_headers.patch
  • fix_mime_version_headers-2.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 2015-09-25.19:47:28.823>
labels = ['type-bug', 'expert-email']
title = 'EmailMessage.add_attachment() creates parts with spurious MIME-Version header.'
updated_at = <Date 2021-01-12.13:38:20.743>
user = 'https://bugs.python.org/groner'

    bugs.python.org fields:

    activity = <Date 2021-01-12.13:38:20.743>
actor = 'eriker'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['email']
creation = <Date 2015-09-25.19:47:28.823>
creator = 'groner'
dependencies = []
files = ['40576', '40577', '40578', '44520', '44644']
hgrepos = []
issue_num = 25235
keywords = ['patch']
message_count = 11.0
messages = ['251600', '251601', '275490', '275552', '275836', '275840', '275963', '276365', '277320', '277337', '384936']
nosy_count = 4.0
nosy_names = ['barry', 'r.david.murray', 'groner', 'eriker']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'commit review'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue25235'
versions = ['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.