email.contentmanager.raw_data_manager bytes handler breaks on 7bit cte
Open
Nobody has claimed this yet.
3.8 (EOL)
stdlib
topic-email
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 39252 |
|---|
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-01-07.22:27:03.821>
labels = ['3.8', 'type-bug', 'library']
title = 'email.contentmanager.raw_data_manager bytes handler breaks on 7bit cte'
updated_at = <Date 2020-01-07.22:27:03.821>
user = 'https://bugs.python.org/rmccampbell7'
bugs.python.org fields:
activity = <Date 2020-01-07.22:27:03.821>
actor = 'rmccampbell7'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2020-01-07.22:27:03.821>
creator = 'rmccampbell7'
dependencies = []
files = []
hgrepos = []
issue_num = 39252
keywords = []
message_count = 1.0
messages = ['359555']
nosy_count = 1.0
nosy_names = ['rmccampbell7']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue39252'
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 reproducing the 7bit CTE failure in email.contentmanager.raw_data_manager and inspect the email library's existing tests. The issue does not name a file or test, so first locate the bytes handler and its coverage. Done means bytes content is handled correctly when the transfer encoding is 7bit.
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
- Needs clarification
- Newbie friendliness
- 35/100