python / python/cpython

Obscure netrc parser "bug"

Open
#78,313 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

3.7 (EOL) 3.8 (EOL) stdlib type-bug
Dominant language
Python
Stars
77.2k
Forks
36k
PR merge metrics
PR metrics pending

Description

BPO 34132
Nosy @smontanaro, @zhangyangyu, @bbayles, @tirkarthi
PRs
  • python/cpython#8320
  • python/cpython#8360
  • Files
  • netrc-comment-blank: working netrc file
  • netrc-blank-comment: problematic netrc file
  • netrc_foo_tester.py
  • 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 2018-07-16.23:13:33.685>
    labels = ['3.7', '3.8', 'type-bug', 'library']
    title = 'Obscure netrc parser "bug"'
    updated_at = <Date 2018-07-21.00:54:36.328>
    user = 'https://github.com/smontanaro'
    

    bugs.python.org fields:

    activity = <Date 2018-07-21.00:54:36.328>
    actor = 'bbayles'
    assignee = 'none'
    closed = False
    closed_date = None
    closer = None
    components = ['Library (Lib)']
    creation = <Date 2018-07-16.23:13:33.685>
    creator = 'skip.montanaro'
    dependencies = []
    files = ['47696', '47697', '47699']
    hgrepos = []
    issue_num = 34132
    keywords = ['patch']
    message_count = 4.0
    messages = ['321779', '321810', '321975', '322053']
    nosy_count = 4.0
    nosy_names = ['skip.montanaro', 'xiang.zhang', 'bbayles', 'xtreak']
    pr_nums = ['8320', '8360']
    priority = 'normal'
    resolution = None
    stage = 'patch review'
    status = 'open'
    superseder = None
    type = 'behavior'
    url = 'https://bugs.python.org/issue34132'
    versions = ['Python 3.6', 'Python 3.7', 'Python 3.8']
    

    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.

    Research direction

    Start by comparing the working netrc-comment-blank and problematic netrc-blank-comment files, then run netrc_foo_tester.py to reproduce the parser behavior. Review the linked PR context and patch-review status before deciding whether any work remains; done requires an agreed behavior and a corresponding regression test.

    Written by the indexing model from the issue text.

    Assessment

    Tech stack
    python
    Domain
    backend
    Issue type
    Bug
    Difficulty
    3/5
    Estimated time
    1-2 days
    Activity status
    Stale
    Clarity
    Needs clarification
    Newbie friendliness
    25/100

    Get new issues in your inbox

    A short digest of beginner-friendly GitHub issues.