Reversing an encoding with unicode-escape returns a different result

未关闭
#65,530 14 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

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

调研方向

Start by reviewing the original BPO issue 21331 and reproducing the unicode-escape behavior described in the title on Python 3.4 or a current checkout. Trace the Unicode codec entry points and existing codec tests; done means reversing the encoding preserves the original result and the behavior is covered by a regression test.

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

描述

topic-unicode type-bug
BPO 21331
Nosy @malemburg, @loewis, @ncoghlan, @vstinner, @ezio-melotti, @bitdancer, @serhiy-storchaka

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 2014-04-22.20:58:23.698>
labels = ['type-bug', 'expert-unicode']
title = 'Reversing an encoding with unicode-escape returns a different result'
updated_at = <Date 2014-06-24.10:08:35.712>
user = 'https://bugs.python.org/Sworddragon'

bugs.python.org fields:

activity = <Date 2014-06-24.10:08:35.712>
actor = 'lemburg'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Unicode']
creation = <Date 2014-04-22.20:58:23.698>
creator = 'Sworddragon'
dependencies = []
files = []
hgrepos = []
issue_num = 21331
keywords = []
message_count = 14.0
messages = ['217021', '217024', '217033', '217055', '217094', '217095', '217096', '218519', '221191', '221198', '221204', '221308', '221442', '221447']
nosy_count = 8.0
nosy_names = ['lemburg', 'loewis', 'ncoghlan', 'vstinner', 'ezio.melotti', 'r.david.murray', 'Sworddragon', 'serhiy.storchaka']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue21331'
versions = ['Python 3.4']

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