email.parser stops parsing headers too soon when given a defective message.

Open
#70,873 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start with the email.parser implementation and the attached continue-header.patch, then reproduce the behavior with a defective message. Trace where header parsing stops and compare the result with the patch's intended change. Done means defective messages continue parsing headers correctly without regressing normal parsing.

Written by the indexing model from the issue text.

Description

stdlib topic-email type-bug
BPO 26686
Nosy @warsaw, @msapiro, @bitdancer, @vadmium
Files
  • continue-header.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 2016-04-01.17:46:30.047>
labels = ['type-bug', 'library', 'expert-email']
title = 'email.parser stops parsing headers too soon when given a defective message.'
updated_at = <Date 2016-08-10.22:57:36.138>
user = 'https://github.com/msapiro'

    bugs.python.org fields:

    activity = <Date 2016-08-10.22:57:36.138>
actor = 'martin.panter'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)', 'email']
creation = <Date 2016-04-01.17:46:30.047>
creator = 'msapiro'
dependencies = []
files = ['43374']
hgrepos = []
issue_num = 26686
keywords = ['patch']
message_count = 7.0
messages = ['262750', '262751', '262776', '268438', '272295', '272332', '272381']
nosy_count = 4.0
nosy_names = ['barry', 'msapiro', 'r.david.murray', 'martin.panter']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue26686'
versions = ['Python 2.7', 'Python 3.5', 'Python 3.6']

    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.