Email part with content type message is multipart.
Open
Nobody has claimed this yet.
3.8 (EOL)
stdlib
topic-email
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
Description
| BPO | 45626 |
|---|---|
| Files |
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 2021-10-27.12:57:54.903>
labels = ['3.8', 'type-bug', 'library']
title = 'Email part with content type message is multipart.'
updated_at = <Date 2021-10-27.12:57:54.903>
user = 'https://bugs.python.org/jdhowroyd'
bugs.python.org fields:
activity = <Date 2021-10-27.12:57:54.903>
actor = 'jdhowroyd'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2021-10-27.12:57:54.903>
creator = 'jdhowroyd'
dependencies = []
files = ['50396']
hgrepos = []
issue_num = 45626
keywords = []
message_count = 1.0
messages = ['405091']
nosy_count = 1.0
nosy_names = ['jdhowroyd']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue45626'
versions = ['Python 3.8']
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the attached 16155.eml example and inspect Python's email library handling of content type message/rfc822. The issue does not name a source file, test, or expected behavior, so clarify the intended multipart semantics before identifying the relevant parser code and regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100