Add unicode script info to the unicode database

Open
#50,580 19 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

Start by reviewing the attached unicode-script.diff, unicode-script-2.diff, and unicode-script-3.diff files, then inspect the current Unicode component and database workflow. Identify the relevant data-generation and test entry points before deciding how the proposed script information fits. Done means the Unicode script data is integrated and the relevant Unicode tests pass.

Written by the indexing model from the issue text.

Description

stdlib topic-unicode type-feature
BPO 6331
Nosy @malemburg, @loewis, @doerwalter, @vstinner, @benjaminp, @ezio-melotti, @akitada, @berkerpeksag, @gnprice
Files
  • unicode-script.diff
  • unicode-script-2.diff
  • unicode-script-3.diff
    		•

    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 2009-06-23.20:50:57.790>
labels = ['type-feature', '3.7', 'expert-unicode']
title = 'Add unicode script info to the unicode database'
updated_at = <Date 2019-08-28.05:09:27.665>
user = 'https://github.com/doerwalter'

    bugs.python.org fields:

    activity = <Date 2019-08-28.05:09:27.665>
actor = 'Greg Price'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Unicode']
creation = <Date 2009-06-23.20:50:57.790>
creator = 'doerwalter'
dependencies = []
files = ['14348', '14356', '14418']
hgrepos = []
issue_num = 6331
keywords = ['patch', 'needs review']
message_count = 17.0
messages = ['89642', '89647', '89671', '89675', '89701', '89973', '111040', '177469', '177506', '214204', '214633', '214636', '226266', '251214', '285269', '320090', '320092']
nosy_count = 13.0
nosy_names = ['lemburg', 'loewis', 'doerwalter', 'vstinner', 'benjamin.peterson', 'ezio.melotti', 'akitada', 'berker.peksag', 'PanderMusubi', 'Elizacat', 'Cosimo Lupo', 'Denis Jacquerye', 'Greg Price']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue6331'
versions = ['Python 3.7']

    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.