EmailMessage mis-folding headers of a certain length
Open
Nobody has claimed this yet.
3.8 (EOL)
topic-email
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 43493 |
|---|---|
| Nosy | @warsaw, @bitdancer, @akulakov, @mglover |
| 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-03-14.20:46:29.071>
labels = ['type-bug', '3.8', 'expert-email']
title = 'EmailMessage mis-folding headers of a certain length'
updated_at = <Date 2021-07-06.17:16:58.719>
user = 'https://github.com/mglover'
bugs.python.org fields:
activity = <Date 2021-07-06.17:16:58.719>
actor = 'r.david.murray'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['email']
creation = <Date 2021-03-14.20:46:29.071>
creator = 'mglover'
dependencies = []
files = ['49875', '49889']
hgrepos = []
issue_num = 43493
keywords = []
message_count = 5.0
messages = ['388687', '388989', '389014', '396884', '397049']
nosy_count = 4.0
nosy_names = ['barry', 'r.david.murray', 'andrei.avk', 'mglover']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue43493'
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 by running header_misfolding.py to reproduce the incorrect behavior, then read foldfix.py and the surrounding email header-folding code. Confirm the expected folding for the affected header lengths and verify that the reproduction no longer shows mis-folded headers.
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
- 35/100