email message get_content throws KeyError for content main types font and model
Open
Nobody has claimed this yet.
3.10
3.7 (EOL)
3.8 (EOL)
3.9 (EOL)
topic-email
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 42054 |
|---|---|
| Nosy | @msapiro |
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-10-16.19:24:02.400>
labels = ['3.7', '3.8', '3.9', '3.10']
title = 'email message get_content throws KeyError for content main types font and model'
updated_at = <Date 2020-10-16.19:24:02.400>
user = 'https://github.com/msapiro'
bugs.python.org fields:
activity = <Date 2020-10-16.19:24:02.400>
actor = 'msapiro'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = []
creation = <Date 2020-10-16.19:24:02.400>
creator = 'msapiro'
dependencies = []
files = []
hgrepos = []
issue_num = 42054
keywords = []
message_count = 1.0
messages = ['378738']
nosy_count = 1.0
nosy_names = ['msapiro']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue42054'
versions = ['Python 3.6', 'Python 3.7', 'Python 3.8', 'Python 3.9', 'Python 3.10']
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 KeyError through email message get_content with the font and model content main types, then inspect the implementation and nearby tests. Determine the expected handling for these types and add regression coverage; done means get_content no longer raises KeyError for either type.
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