netrc module does not handle multiple entries for a single host

Open
#55,625 31 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
networking

Research direction

Review the existing python/cpython#17823 pull request and the linked netrc.patch and issue11416.diff files first. Confirm the expected behavior for multiple entries for one host and inspect any tests or documentation changes included there; done means the netrc module handles those entries correctly without regressing existing behavior.

Written by the indexing model from the issue text.

Description

3.15 stdlib type-feature
BPO 11416
Nosy @rhettinger, @merwok, @bitdancer, @briancurtin, @berkerpeksag, @arsyee
PRs
  • python/cpython#17823
  • Files
  • netrc.patch
  • netrc-doc.patch
  • issue11416.diff
  • netrc.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 2011-03-06.21:14:07.137>
    labels = ['3.7', '3.8', 'type-feature', 'library']
    title = 'netrc module does not handle multiple entries for a single host'
    updated_at = <Date 2020-01-04.19:47:56.142>
    user = 'https://bugs.python.org/saffroy'
    

    bugs.python.org fields:

    activity = <Date 2020-01-04.19:47:56.142>
    actor = 'Frew Schmidt'
    assignee = 'none'
    closed = False
    closed_date = None
    closer = None
    components = ['Library (Lib)']
    creation = <Date 2011-03-06.21:14:07.137>
    creator = 'saffroy'
    dependencies = []
    files = ['22195', '22204', '34485', '42510']
    hgrepos = []
    issue_num = 11416
    keywords = ['patch', 'needs review']
    message_count = 27.0
    messages = ['130193', '130618', '130686', '130689', '132421', '132422', '132434', '137218', '137267', '137276', '137277', '137278', '137279', '137280', '137282', '137283', '137288', '137289', '137341', '137449', '138071', '213229', '213247', '213955', '263699', '358788', '359297']
    nosy_count = 9.0
    nosy_names = ['rhettinger', 'eric.araujo', 'r.david.murray', 'brian.curtin', 'saffroy', 'berker.peksag', 'Yuri.Bochkarev', 'luc', 'arsyee']
    pr_nums = ['17823']
    priority = 'normal'
    resolution = None
    stage = 'patch review'
    status = 'open'
    superseder = None
    type = 'enhancement'
    url = 'https://bugs.python.org/issue11416'
    versions = ['Python 2.7', 'Python 3.5', 'Python 3.6', 'Python 3.7', 'Python 3.8']
    

    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.