More fully implement Unicode's case mappings

Open
#82,029 10 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
internationalization

Research direction

The issue identifies Python's Unicode component and the migrated BPO issue 37848, but names no files or tests. Start by reviewing the existing Unicode case-mapping implementation and the requirements in issue 37848; done means Unicode case mappings are implemented more fully and covered by appropriate tests.

Written by the indexing model from the issue text.

Description

3.9 (EOL) topic-unicode
BPO 37848
Nosy @malemburg, @vstinner, @benjaminp, @ezio-melotti, @serhiy-storchaka, @gnprice

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 2019-08-14.05:42:20.920>
labels = ['3.9', 'expert-unicode']
title = "More fully implement Unicode's case mappings"
updated_at = <Date 2019-08-15.01:15:14.210>
user = 'https://github.com/gnprice'

bugs.python.org fields:

activity = <Date 2019-08-15.01:15:14.210>
actor = 'benjamin.peterson'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Unicode']
creation = <Date 2019-08-14.05:42:20.920>
creator = 'Greg Price'
dependencies = []
files = []
hgrepos = []
issue_num = 37848
keywords = []
message_count = 9.0
messages = ['349646', '349649', '349659', '349660', '349669', '349732', '349733', '349738', '349782']
nosy_count = 6.0
nosy_names = ['lemburg', 'vstinner', 'benjamin.peterson', 'ezio.melotti', 'serhiy.storchaka', 'Greg Price']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue37848'
versions = ['Python 3.9']

Dominant language
Python
Stars
77.2k
Forks
36k
Avg merge
1d 9h
Merged PRs (30d)
558

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from python/cpython

All issues in python/cpython

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.