Add to unicodedata a function to query the "Quick_Check" property for a character

Open
#67,738 12 comments 0 reactions 0 assignees View on GitHub

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
api

Research direction

Start by reviewing the unicodedata entry point, unicodedata_db.h, and the successive quick_check_x.patch, quick_check_2.patch, quick_check_3.patch, and quick_check_4.diff files. Compare the final patch with current Unicode data handling and existing unicodedata tests. Done means the Quick_Check property can be queried through the public API with suitable coverage.

Written by the indexing model from the issue text.

Description

stdlib topic-unicode type-feature
BPO 23550
Nosy @malemburg, @loewis, @pitrou, @vstinner, @benjaminp, @ezio-melotti, @berkerpeksag
Files
  • quick_check_x.patch: Initial attempt at implementation
  • quick_check_2.patch: Better patch that includes changes to unicodedata_db.h
  • quick_check_3.patch: Patch addressing some issues raised by reviewers
  • quick_check_4.diff: Patch that makes all requested stylistic changes
    		•

    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 2015-02-28.18:21:10.024>
labels = ['type-feature', 'library', 'expert-unicode']
title = 'Add to unicodedata a function to query the "Quick_Check" property for a character'
updated_at = <Date 2015-03-28.19:25:31.677>
user = 'https://bugs.python.org/Hammerite'

    bugs.python.org fields:

    activity = <Date 2015-03-28.19:25:31.677>
actor = 'Hammerite'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)', 'Unicode']
creation = <Date 2015-02-28.18:21:10.024>
creator = 'Hammerite'
dependencies = []
files = ['38308', '38323', '38705', '38719']
hgrepos = []
issue_num = 23550
keywords = ['patch']
message_count = 12.0
messages = ['236901', '236910', '236913', '237094', '237165', '238484', '238487', '238556', '239185', '239356', '239441', '239463']
nosy_count = 8.0
nosy_names = ['lemburg', 'loewis', 'pitrou', 'vstinner', 'benjamin.peterson', 'ezio.melotti', 'berker.peksag', 'Hammerite']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue23550'
versions = ['Python 3.5']

    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.