Message from BytesParser cannot be flattened immediately
Open
Nobody has claimed this yet.
3.9 (EOL)
topic-email
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 44694 |
|---|---|
| Nosy | @warsaw, @bitdancer |
| 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-07-21.11:06:27.651>
labels = ['type-bug', 'expert-email', '3.9']
title = 'Message from BytesParser cannot be flattened immediately'
updated_at = <Date 2021-07-24.12:09:28.261>
user = 'https://bugs.python.org/vitas1'
bugs.python.org fields:
activity = <Date 2021-07-24.12:09:28.261>
actor = 'vitas1'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['email']
creation = <Date 2021-07-21.11:06:27.651>
creator = 'vitas1'
dependencies = []
files = ['50178']
hgrepos = []
issue_num = 44694
keywords = []
message_count = 2.0
messages = ['397937', '398109']
nosy_count = 3.0
nosy_names = ['barry', 'r.david.murray', 'vitas1']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue44694'
versions = ['Python 3.9']
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 by examining the attached 0.msg and the email component's BytesParser behavior, then reproduce the reported failure when flattening the parsed message immediately. Trace the relevant parser and flattening entry points and identify the expected behavior; the issue is done when the message can be flattened immediately without regression.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100