Email header with ;;;; stuffing takes very long to parse

未关闭
#87,075 3 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
35/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
停滞
技术栈
python
领域
performance

调研方向

从链接的 repro.py 脚本开始并运行它,以重现电子邮件标头解析变慢的问题。跟踪电子邮件组件的解析路径以确定原因,然后验证 repro 是否能在一秒内完成;如果能找到相关的测试位置,则添加或更新回归测试。

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

描述

3.12 performance topic-email
BPO 42909
Nosy @warsaw, @bitdancer, @akulakov, @eriker-fsc
Files
  • repro.py: Simple self-contained repro script - should take less than 1s but takes more than 30
  • 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-01-12.13:13:10.953>
    labels = ['3.8', 'expert-email', '3.10', 'performance', '3.7', '3.9']
    title = 'Email header with ;;;; stuffing takes very long to parse'
    updated_at = <Date 2021-07-09.22:18:24.963>
    user = 'https://github.com/eriker-fsc'
    

    bugs.python.org fields:

    activity = <Date 2021-07-09.22:18:24.963>
    actor = 'andrei.avk'
    assignee = 'none'
    closed = False
    closed_date = None
    closer = None
    components = ['email']
    creation = <Date 2021-01-12.13:13:10.953>
    creator = 'eriker'
    dependencies = []
    files = ['49736']
    hgrepos = []
    issue_num = 42909
    keywords = []
    message_count = 3.0
    messages = ['384931', '384938', '397228']
    nosy_count = 4.0
    nosy_names = ['barry', 'r.david.murray', 'andrei.avk', 'eriker']
    pr_nums = []
    priority = 'normal'
    resolution = None
    stage = None
    status = 'open'
    superseder = None
    type = 'resource usage'
    url = 'https://bugs.python.org/issue42909'
    versions = ['Python 3.6', 'Python 3.7', 'Python 3.8', 'Python 3.9', 'Python 3.10']
    

    主要语言
    Python
    星标
    77.2k
    派生
    36k
    平均合并
    1 天 9 小时
    30 天内合并 PR
    558

    贡献指南

    打开贡献指南

    从这里开始

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

    python/cpython 的其他 Issue

    查看 python/cpython 的全部 Issue

    相似的 Issue

    更多 Python Issue

    把新 issue 发到你的邮箱

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