New sequences for Unicode groups and block ranges needed

Open
#43,715 17 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
Quiet
Tech stack
python

Research direction

Start by reviewing dependency bpo-2636 and the Regular Expressions and Unicode components; the payload names no files or tests. Determine the required Unicode group and block-range sequences from the issue history, then identify the relevant implementation and test locations before defining completion.

Written by the indexing model from the issue text.

Description

extension-modules topic-regex topic-unicode type-feature
BPO 1528154
Nosy @malemburg, @loewis, @terryjreedy, @devdanzin, @ezio-melotti
Dependencies
  • bpo-2636: Adding a new regex module (compatible with re)
  • 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 2006-07-25.04:44:06.000>
    labels = ['expert-regex', 'type-feature', 'expert-unicode']
    title = 'New sequences for Unicode groups and block ranges needed'
    updated_at = <Date 2019-03-15.23:59:53.114>
    user = 'https://bugs.python.org/gmarketer'
    

    bugs.python.org fields:

    activity = <Date 2019-03-15.23:59:53.114>
    actor = 'BreamoreBoy'
    assignee = 'none'
    closed = False
    closed_date = None
    closer = None
    components = ['Regular Expressions', 'Unicode']
    creation = <Date 2006-07-25.04:44:06.000>
    creator = 'gmarketer'
    dependencies = ['2636']
    files = []
    hgrepos = []
    issue_num = 1528154
    keywords = []
    message_count = 15.0
    messages = ['54861', '54862', '54863', '54864', '54865', '54866', '84503', '84532', '84544', '100129', '130412', '185757', '185759', '221632', '221761']
    nosy_count = 8.0
    nosy_names = ['lemburg', 'loewis', 'effbot', 'terry.reedy', 'ajaksu2', 'gmarketer', 'ezio.melotti', 'mrabarnett']
    pr_nums = []
    priority = 'normal'
    resolution = None
    stage = 'test needed'
    status = 'open'
    superseder = None
    type = 'enhancement'
    url = 'https://bugs.python.org/issue1528154'
    versions = ['Python 3.4']
    

    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.