email/charset.py convert() patch

未关闭
#42,985 6 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

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

调研方向

Start by reading email/charset.py and the attached charset.py.patch to understand the proposed convert() change. Use ja-nonlegit.py as the example input and compare its behavior with the patch; done means the intended character conversion behavior is defined and supported without regressing existing email handling.

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

描述

stdlib topic-email type-feature
BPO 1443875
Nosy @loewis, @warsaw, @vstinner, @bitdancer
Files
  • charset.py.patch: charset.py.patch
  • ja-nonlegit.py: non-legitimate ja characters 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 2006-03-06.04:41:30.000>
labels = ['type-feature', 'library', 'expert-email']
title = 'email/charset.py convert() patch'
updated_at = <Date 2019-07-29.12:00:52.206>
user = 'https://bugs.python.org/tkikuchi'

    bugs.python.org fields:

    activity = <Date 2019-07-29.12:00:52.206>
actor = 'vstinner'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)', 'email']
creation = <Date 2006-03-06.04:41:30.000>
creator = 'tkikuchi'
dependencies = []
files = ['7052', '7053']
hgrepos = []
issue_num = 1443875
keywords = ['patch']
message_count = 6.0
messages = ['49660', '49661', '49662', '49663', '49664', '348645']
nosy_count = 5.0
nosy_names = ['loewis', 'barry', 'tkikuchi', 'vstinner', 'r.david.murray']
pr_nums = []
priority = 'low'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue1443875'
versions = ['Python 3.3']

    主要语言
    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 摘要。