email.Message param parsing problem II

Open
#39,128 12 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start with the archived issue795081.patch and the virus5 example, then inspect the email library's Message parameter parsing entry point. The issue text does not specify the expected parsing result, so use the archived materials and linked PR gh-141702 to determine scope; done means the intended behavior is covered and the relevant tests pass.

Written by the indexing model from the issue text.

Description

stdlib topic-email type-feature
BPO 795081
Nosy @warsaw, @devdanzin, @bitdancer, @zvyn
Files
  • virus5: Example (deactivated) virus with wierd headers
  • issue795081.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 2003-08-26.03:37:10.000>
labels = ['easy', 'type-feature', 'library', 'expert-email']
title = 'email.Message param parsing problem II'
updated_at = <Date 2016-12-12.12:01:53.266>
user = 'https://bugs.python.org/customdesigned'

    bugs.python.org fields:

    activity = <Date 2016-12-12.12:01:53.266>
actor = 'bpoaugust'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)', 'email']
creation = <Date 2003-08-26.03:37:10.000>
creator = 'customdesigned'
dependencies = []
files = ['8230', '39701']
hgrepos = []
issue_num = 795081
keywords = ['patch', 'easy']
message_count = 9.0
messages = ['53986', '53987', '53988', '53989', '63201', '82025', '245292', '245317', '282986']
nosy_count = 8.0
nosy_names = ['barry', 'collinwinter', 'customdesigned', 'tony_nelson', 'ajaksu2', 'r.david.murray', 'bpoaugust', 'zvyn']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'test needed'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue795081'
versions = ['Python 3.3']

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