Add support for emoji-data.txt and emoji-variation-sequences.txt to unicodedata
Open
Nobody has claimed this yet.
stdlib
topic-unicode
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 41622 |
|---|---|
| Nosy | @terryjreedy, @ezio-melotti, @jack1142 |
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-08-23.20:34:50.618>
labels = ['3.10', 'type-feature', '3.9', 'expert-unicode']
title = 'Add support for emoji-data.txt and emoji-variation-sequences.txt to unicodedata'
updated_at = <Date 2020-09-01.09:46:27.836>
user = 'https://github.com/jack1142'
bugs.python.org fields:
activity = <Date 2020-09-01.09:46:27.836>
actor = 'vstinner'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Unicode']
creation = <Date 2020-08-23.20:34:50.618>
creator = 'jack1142'
dependencies = []
files = []
hgrepos = []
issue_num = 41622
keywords = []
message_count = 2.0
messages = ['375826', '376084']
nosy_count = 3.0
nosy_names = ['terry.reedy', 'ezio.melotti', 'jack1142']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue41622'
versions = ['Python 3.9', 'Python 3.10']
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.
Research direction
Start by reading the unicodedata implementation and how its existing Unicode data is incorporated. Compare the requested emoji-data.txt and emoji-variation-sequences.txt inputs with the current supported data, then verify that the resulting unicodedata support covers both files.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100