email header indentation destroyed
Open
Nobody has claimed this yet.
stdlib
topic-email
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 27256 |
|---|---|
| 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 2016-06-07.19:14:46.713>
labels = ['type-bug', 'expert-email']
title = 'email header indentation destroyed'
updated_at = <Date 2016-06-16.15:33:50.562>
user = 'https://bugs.python.org/frispete'
bugs.python.org fields:
activity = <Date 2016-06-16.15:33:50.562>
actor = 'frispete'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['email']
creation = <Date 2016-06-07.19:14:46.713>
creator = 'frispete'
dependencies = []
files = ['43285', '43286', '43417']
hgrepos = []
issue_num = 27256
keywords = []
message_count = 3.0
messages = ['267732', '267916', '268675']
nosy_count = 3.0
nosy_names = ['barry', 'frispete', 'r.david.murray']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'test needed'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue27256'
versions = ['Python 3.5', 'Python 3.6']
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 comparing the supplied utf8-header-failure.mail input with mf.9__mi0bf.out, then read email_flatten.py to trace how BytesGenerator.flatten changes the headers. Use the existing email tests as the place to add coverage, and consider the issue done when the reproduced header indentation is preserved in the generated message.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100