email.Utils.parseaddr fails to parse valid addresses

Open
#40,889 10 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

The issue identifies email.Utils.parseaddr as the entry point; start there and review the linked historical PRs (142, 6917, and gh-123311). The payload names no file or test, so completion should be established by reproducing the valid-address failure and confirming the parser handles those cases.

Written by the indexing model from the issue text.

Description

stdlib topic-email type-bug
BPO 1025395
Nosy @warsaw, @tiran, @merwok, @bitdancer, @vadmium, @thehesiod, @ioanatia
PRs
  • python/cpython#142
  • python/cpython#6917
    		•

    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 2004-09-09.20:43:42.000>
labels = ['3.7', 'type-bug', 'library', 'expert-email']
title = 'email.Utils.parseaddr fails to parse valid addresses'
updated_at = <Date 2018-05-16.19:01:00.100>
user = 'https://bugs.python.org/melicertes'

    bugs.python.org fields:

    activity = <Date 2018-05-16.19:01:00.100>
actor = 'ioanatia'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)', 'email']
creation = <Date 2004-09-09.20:43:42.000>
creator = 'melicertes'
dependencies = []
files = []
hgrepos = []
issue_num = 1025395
keywords = ['patch']
message_count = 10.0
messages = ['22413', '59669', '59670', '59671', '59735', '59737', '59751', '59753', '301485', '301504']
nosy_count = 10.0
nosy_names = ['barry', 'melicertes', 'christian.heimes', 'sdgathman', 'eric.araujo', 'r.david.murray', 'sascha_silbe', 'martin.panter', 'thehesiod', 'ioanatia']
pr_nums = ['142', '6917']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue1025395'
versions = ['Python 2.7', 'Python 3.2', 'Python 3.3', 'Python 3.6', 'Python 3.7']

    Linked PRs
    • gh-123311
    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.