Add Japanese legacy encodings
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- python
- Domain
- internationalization
Research direction
Start by reviewing the linked add-japanese-legacy-encoding1.patch and the existing standard-library encoding implementations it extends. Check the patch against the requested Japanese legacy encodings and verify the relevant encoding behavior with the existing test suite; done means the encodings are added and covered without regressions.
Written by the indexing model from the issue text.
Description
| BPO | 23050 |
|---|---|
| Nosy | @malemburg, @loewis, @atsuoishimoto, @vstinner, @bitdancer, @methane, @serhiy-storchaka |
| 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 2014-12-14.14:34:49.245>
labels = ['type-feature', 'library']
title = 'Add Japanese legacy encodings'
updated_at = <Date 2014-12-16.04:18:44.759>
user = 'https://bugs.python.org/t2y'
bugs.python.org fields:
activity = <Date 2014-12-16.04:18:44.759>
actor = 't2y'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2014-12-14.14:34:49.245>
creator = 't2y'
dependencies = []
files = ['37447']
hgrepos = ['285']
issue_num = 23050
keywords = ['patch']
message_count = 9.0
messages = ['232638', '232639', '232640', '232668', '232674', '232684', '232685', '232702', '232707']
nosy_count = 8.0
nosy_names = ['lemburg', 'loewis', 'ishimoto', 'vstinner', 'r.david.murray', 'methane', 'serhiy.storchaka', 't2y']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue23050'
versions = ['Python 3.5']
- 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
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
🐛 Bug 🔔 Pending processing
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
jumpserver/jumpserver#17584 ·