EmailMessage.as_string is altering the message state and actually fix bugs
Open
Nobody has claimed this yet.
3.7 (EOL)
3.8 (EOL)
topic-email
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
Description
| BPO | 41145 |
|---|---|
| Nosy | @warsaw, @bitdancer, @mardiros |
| 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 2020-06-28.09:43:33.284>
labels = ['3.8', 'type-bug', '3.7', 'expert-email']
title = 'EmailMessage.as_string is altering the message state and actually fix bugs'
updated_at = <Date 2020-07-10.16:58:06.348>
user = 'https://github.com/mardiros'
bugs.python.org fields:
activity = <Date 2020-07-10.16:58:06.348>
actor = 'r.david.murray'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['email']
creation = <Date 2020-06-28.09:43:33.284>
creator = 'mardiros'
dependencies = []
files = ['49271']
hgrepos = []
issue_num = 41145
keywords = []
message_count = 2.0
messages = ['372508', '373472']
nosy_count = 3.0
nosy_names = ['barry', 'r.david.murray', 'mardiros']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue41145'
versions = ['Python 3.7', '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 bug.py reproduction and the EmailMessage.as_string behavior described in the issue. Trace how serialization changes message state and identify the reported bugs before deciding the needed scope. Done means the reproduction no longer alters state and the reported bugs are fixed, with coverage for the demonstrated behavior.
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
- 25/100