python / python/cpython

email.parse part.get_filename() fails to unwrap long attachment file names (legacy API)

未关闭
#84,539 7 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

topic-email
主要语言
Python
星标
77.2k
派生
36k
PR 合并指标
PR 指标待抓取

描述

BPO 40359
Nosy @warsaw, @bitdancer
Files
  • mwe.py: python script with minimal working example
  • 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 2020-04-22.00:26:27.411>
    labels = ['expert-email']
    title = 'email.parse part.get_filename() fails to unwrap long attachment file names (legacy API)'
    updated_at = <Date 2020-04-28.12:27:30.371>
    user = 'https://bugs.python.org/matt-davis'
    

    bugs.python.org fields:

    activity = <Date 2020-04-28.12:27:30.371>
    actor = 'r.david.murray'
    assignee = 'none'
    closed = False
    closed_date = None
    closer = None
    components = ['email']
    creation = <Date 2020-04-22.00:26:27.411>
    creator = 'matt-davis'
    dependencies = []
    files = ['49083']
    hgrepos = []
    issue_num = 40359
    keywords = []
    message_count = 6.0
    messages = ['366963', '366965', '366966', '367117', '367493', '367523']
    nosy_count = 3.0
    nosy_names = ['barry', 'r.david.murray', 'matt-davis']
    pr_nums = []
    priority = 'normal'
    resolution = None
    stage = None
    status = 'open'
    superseder = None
    type = None
    url = 'https://bugs.python.org/issue40359'
    versions = ['Python 3.6']
    

    贡献指南

    打开贡献指南

    从这里开始

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

    调研方向

    从链接的最小可运行示例 mwe.py 开始,通过 email.parse 和 part.get_filename() 重现该失败,重点关注旧版 email API。跟踪长附件文件名的处理方式,并验证完成后的行为能够正确解包该文件名,同时不会导致现有文件名解析出现回归。

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

    评估

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

    把新 issue 发到你的邮箱

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