[doc] email.parser.BytesParser - parse and parsebytes work not equivalent

Open
#83,252 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start with the email.parser.BytesParser documentation and compare the parse and parsebytes behavior using the attached test.eml message and test.py script. Confirm what distinction the existing documentation leaves unexplained; done means the relevant documentation clearly describes the two methods and their behavior.

Written by the indexing model from the issue text.

Description

3.10 3.11 3.9 (EOL) docs topic-email
BPO 39071
Nosy @warsaw, @bitdancer, @maxking, @manfred-kaiser, @iritkatriel
Files
  • test.eml: Test Mail with 2 mime parts (html and plain text)
  • test.py: Testscript for creating the hash values
    		•

    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 2019-12-17.08:32:29.462>
labels = ['3.9', '3.11', 'expert-email', '3.10', 'docs']
title = '[doc] email.parser.BytesParser - parse and parsebytes work not equivalent'
updated_at = <Date 2021-12-12.19:52:30.416>
user = 'https://github.com/manfred-kaiser'

    bugs.python.org fields:

    activity = <Date 2021-12-12.19:52:30.416>
actor = 'iritkatriel'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation', 'email']
creation = <Date 2019-12-17.08:32:29.462>
creator = 'mkaiser'
dependencies = []
files = ['48785', '48786']
hgrepos = []
issue_num = 39071
keywords = []
message_count = 5.0
messages = ['358533', '358566', '358570', '358571', '408408']
nosy_count = 6.0
nosy_names = ['barry', 'r.david.murray', 'docs@python', 'maxking', 'mkaiser', 'iritkatriel']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue39071'
versions = ['Python 3.9', 'Python 3.10', 'Python 3.11']

    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.