Incorrect handling of unicode character \U00010900
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 15/100
Research direction
Review the reported character-handling behavior and the attached selection.png, then inspect linked PR gh-144744 for the current implementation context. Done means the handling of Unicode character U+10900 matches the expected behavior and the relevant regression coverage passes.
Written by the indexing model from the issue text.
Description
| BPO | 45105 |
|---|---|
| Nosy | @ronaldoussoren, @ezio-melotti, @stevendaprano, @serhiy-storchaka, @eryksun, @maxbachmann |
| Files |
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-09-05.11:12:09.498>
labels = ['type-bug', '3.9', 'expert-unicode']
title = 'Incorrect handling of unicode character \\U00010900'
updated_at = <Date 2021-09-12.08:57:14.225>
user = 'https://github.com/maxbachmann'
bugs.python.org fields:
activity = <Date 2021-09-12.08:57:14.225>
actor = 'serhiy.storchaka'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Unicode']
creation = <Date 2021-09-05.11:12:09.498>
creator = 'maxbachmann'
dependencies = []
files = ['50260']
hgrepos = []
issue_num = 45105
keywords = []
message_count = 12.0
messages = ['401078', '401079', '401082', '401083', '401084', '401086', '401088', '401090', '401092', '401095', '401656', '401658']
nosy_count = 6.0
nosy_names = ['ronaldoussoren', 'ezio.melotti', 'steven.daprano', 'serhiy.storchaka', 'eryksun', 'maxbachmann']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue45105'
versions = ['Python 3.6', 'Python 3.9']
Linked PRs
- gh-144744
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from python/cpython
-
docs pending
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
build type-bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
stdlib topic-email type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Similar issues
-
🐛 Bug 🔔 Pending processing
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
jumpserver/jumpserver#17584 ·
-
link-check link-check:sphinx-theme
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
modelscope/DiffSynth-Studio#1702 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
qgis/QGIS-Documentation#11275 ·
-
bug priority:normal ready-for-dev
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
OpenHands/extensions#626 · 1 comment ·