EmailMessage utf-8 folding error
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 | 45551 |
|---|---|
| Nosy | @warsaw, @bitdancer, @andrzejQ |
| 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-21.11:18:06.549>
labels = ['type-bug', 'expert-email', '3.9']
title = 'EmailMessage utf-8 folding error'
updated_at = <Date 2021-10-22.13:58:56.178>
user = 'https://github.com/andrzejQ'
bugs.python.org fields:
activity = <Date 2021-10-22.13:58:56.178>
actor = 'r.david.murray'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['email']
creation = <Date 2021-10-21.11:18:06.549>
creator = 'andrzejQ'
dependencies = []
files = ['50380']
hgrepos = []
issue_num = 45551
keywords = []
message_count = 2.0
messages = ['404583', '404770']
nosy_count = 3.0
nosy_names = ['barry', 'r.david.murray', 'andrzejQ']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue45551'
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 the attached ERROR_folding_in_EmailMessage.py reproducer and the Python email component; confirm how EmailMessage folds UTF-8 content around a comma. The work is done when the missing whitespace is consistently present after folding and the reported behavior is covered by a regression check.
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
- Mostly clear
- Newbie friendliness
- 35/100