rlcompleter.Completer matches too much

Open
#66,339 10 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
cli

Research direction

Start at the rlcompleter.Completer entry point and review the uploaded rlcompleter.diff and rlcompleter_22141.patch. Check how the completion regular expression captures attributes, then verify that matching no longer includes extra text while preserving the intended completion behavior.

Written by the indexing model from the issue text.

Description

stdlib type-bug
BPO 22141
Nosy @rbtcollins, @bitdancer, @PCManticore, @vadmium
Files
  • rlcompleter.diff: change regular expression to capture the entire attribute
  • rlcompleter_22141.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 2014-08-05.15:59:59.357>
    labels = ['type-bug', 'library']
    title = 'rlcompleter.Completer matches too much'
    updated_at = <Date 2016-05-13.12:11:01.286>
    user = 'https://bugs.python.org/donlorenzo'
    

    bugs.python.org fields:

    activity = <Date 2016-05-13.12:11:01.286>
    actor = 'martin.panter'
    assignee = 'none'
    closed = False
    closed_date = None
    closer = None
    components = ['Library (Lib)']
    creation = <Date 2014-08-05.15:59:59.357>
    creator = 'donlorenzo'
    dependencies = []
    files = ['36269', '37064']
    hgrepos = []
    issue_num = 22141
    keywords = ['patch']
    message_count = 10.0
    messages = ['224848', '224853', '227581', '227603', '230208', '230267', '236418', '247502', '247601', '265469']
    nosy_count = 5.0
    nosy_names = ['rbcollins', 'donlorenzo', 'r.david.murray', 'Claudiu.Popa', 'martin.panter']
    pr_nums = []
    priority = 'normal'
    resolution = None
    stage = 'patch review'
    status = 'open'
    superseder = None
    type = 'behavior'
    url = 'https://bugs.python.org/issue22141'
    versions = ['Python 2.7', 'Python 3.4', '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.