Option for regex groupdict() to show only matching names

Open
#59,196 8 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
Needs clarification
Activity status
Stale
Tech stack
python
Domain
backend

Research direction

Start by reviewing the linked re_groupdict_no_default_future_warning.patch and the original BPO issue 14991, then inspect the regular-expression implementation and tests related to groupdict(). Done means the requested option is implemented with documented behavior and covered by tests, but the payload does not identify those source or test files.

Written by the indexing model from the issue text.

Description

3.7 (EOL) topic-regex type-feature
BPO 14991
Nosy @rhettinger, @larryhastings, @ned-deily, @ezio-melotti, @serhiy-storchaka
Files
  • re_groupdict_no_default_future_warning.patch
    		•

    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 2012-06-03.17:01:00.500>
labels = ['expert-regex', 'type-feature', '3.7']
title = 'Option for regex groupdict() to show only matching names'
updated_at = <Date 2016-10-17.01:57:15.162>
user = 'https://github.com/rhettinger'

    bugs.python.org fields:

    activity = <Date 2016-10-17.01:57:15.162>
actor = 'mrabarnett'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Regular Expressions']
creation = <Date 2012-06-03.17:01:00.500>
creator = 'rhettinger'
dependencies = []
files = ['45120']
hgrepos = []
issue_num = 14991
keywords = ['patch']
message_count = 8.0
messages = ['162223', '163015', '163077', '163081', '278756', '278777', '278789', '278790']
nosy_count = 6.0
nosy_names = ['rhettinger', 'larry', 'ned.deily', 'ezio.melotti', 'mrabarnett', 'serhiy.storchaka']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue14991'
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.