email.contentmanager should use IANA encoding
Open
Nobody has claimed this yet.
3.7 (EOL)
stdlib
topic-email
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 34459 |
|---|---|
| Nosy | @warsaw, @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 2018-08-22.09:00:20.174>
labels = ['3.7', 'expert-email']
title = 'email.contentmanager should use IANA encoding'
updated_at = <Date 2018-08-22.09:18:02.042>
user = 'https://bugs.python.org/era'
bugs.python.org fields:
activity = <Date 2018-08-22.09:18:02.042>
actor = 'era'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['email']
creation = <Date 2018-08-22.09:00:20.174>
creator = 'era'
dependencies = []
files = []
hgrepos = []
issue_num = 34459
keywords = []
message_count = 2.0
messages = ['323869', '323871']
nosy_count = 3.0
nosy_names = ['barry', 'r.david.murray', 'era']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue34459'
versions = ['Python 3.7']
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
The issue identifies email.contentmanager but names no file or test. Start by locating that component and inspect how it handles encodings, then determine where IANA encoding names should be used. Done means email.contentmanager consistently uses IANA encoding identifiers and the relevant behavior is covered by tests.
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
- 35/100