python / python/cpython

Email part with content type message is multipart.

未关闭
#89,789 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

3.8 (EOL) stdlib topic-email type-bug
主要语言
Python
星标
77.2k
派生
36k
平均合并
1 天 9 小时
30 天内合并 PR
558

描述

BPO 45626
Files
  • 16155.eml: Example email
  • 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 2021-10-27.12:57:54.903>
    labels = ['3.8', 'type-bug', 'library']
    title = 'Email part with content type message is multipart.'
    updated_at = <Date 2021-10-27.12:57:54.903>
    user = 'https://bugs.python.org/jdhowroyd'
    

    bugs.python.org fields:

    activity = <Date 2021-10-27.12:57:54.903>
    actor = 'jdhowroyd'
    assignee = 'none'
    closed = False
    closed_date = None
    closer = None
    components = ['Library (Lib)']
    creation = <Date 2021-10-27.12:57:54.903>
    creator = 'jdhowroyd'
    dependencies = []
    files = ['50396']
    hgrepos = []
    issue_num = 45626
    keywords = []
    message_count = 1.0
    messages = ['405091']
    nosy_count = 1.0
    nosy_names = ['jdhowroyd']
    pr_nums = []
    priority = 'normal'
    resolution = None
    stage = None
    status = 'open'
    superseder = None
    type = 'behavior'
    url = 'https://bugs.python.org/issue45626'
    versions = ['Python 3.8']
    

    贡献指南

    打开贡献指南

    从这里开始

    1. 先读完整个 Issue,再读项目的贡献指南。
    2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
    3. Fork 仓库,在一个分支上完成修改。
    4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

    调研方向

    从随附的 16155.eml 示例开始,检查 Python 的 email 库如何处理 content type message/rfc822。该 issue 没有指定源文件、测试或预期行为,因此请先明确预期的 multipart 语义,再确定相关的解析器代码和回归测试。

    由索引模型根据 Issue 内容生成。

    评估

    技术栈
    python
    领域
    backend
    Issue 类型
    缺陷
    难度
    3/5
    预计耗时
    1-2 天
    活跃度
    停滞
    描述清晰度
    需要澄清
    新手友好度
    30/100

    把新 issue 发到你的邮箱

    精选适合新手参与的 GitHub issue 摘要。