"email.message.Message.as_bytes": fails to correctly handle "charset"
未关闭
还没有人认领这个 Issue。
3.9 (EOL)
topic-email
type-bug
- 主要语言
- Python
- 星标
- 77.2k
- 派生
- 36k
- PR 合并指标
- PR 指标待抓取
描述
| BPO | 41307 |
|---|---|
| Nosy | @warsaw, @d-maurer, @bitdancer |
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-07-15.19:18:03.191>
labels = ['type-bug', 'expert-email', '3.9']
title = '"email.message.Message.as_bytes": fails to correctly handle "charset"'
updated_at = <Date 2020-07-15.20:40:58.721>
user = 'https://github.com/d-maurer'
bugs.python.org fields:
activity = <Date 2020-07-15.20:40:58.721>
actor = 'dmaurer'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['email']
creation = <Date 2020-07-15.19:18:03.191>
creator = 'dmaurer'
dependencies = []
files = []
hgrepos = []
issue_num = 41307
keywords = []
message_count = 2.0
messages = ['373711', '373724']
nosy_count = 3.0
nosy_names = ['barry', 'dmaurer', 'r.david.murray']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue41307'
versions = ['Python 3.9']
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
从 email.message.Message.as_bytes 和链接的 BPO issue 41307 开始,然后检查 email 组件现有的测试以及 charset 处理。复现报告的失败,并添加覆盖,表明 as_bytes 能正确处理 charset;在修复该行为且不破坏现有 email 测试后,即可视为完成。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- python
- 领域
- backend
- Issue 类型
- 缺陷
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 活跃度
- 停滞
- 描述清晰度
- 需要澄清
- 新手友好度
- 30/100