"email.message.Message.as_bytes": fails to correctly handle "charset"
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 | 41307 |
|---|---|
| Nosy | @warsaw, @d-maurer, @bitdancer |
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-07-15.19:18:03.191>
labels = ['type-bug', 'expert-email', '3.9']
title = '"email.message.Message.as_bytes": fails to correctly handle "charset"'
updated_at = <Date 2020-07-15.20:40:58.721>
user = 'https://github.com/d-maurer'
bugs.python.org fields:
activity = <Date 2020-07-15.20:40:58.721>
actor = 'dmaurer'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['email']
creation = <Date 2020-07-15.19:18:03.191>
creator = 'dmaurer'
dependencies = []
files = []
hgrepos = []
issue_num = 41307
keywords = []
message_count = 2.0
messages = ['373711', '373724']
nosy_count = 3.0
nosy_names = ['barry', 'dmaurer', 'r.david.murray']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue41307'
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 with email.message.Message.as_bytes and the linked BPO issue 41307, then inspect the email component's existing tests and charset handling. Reproduce the reported failure and add coverage showing that as_bytes correctly handles charset; done means the behavior is fixed without breaking existing email tests.
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
- 30/100