mailbox: It would be nice to move mailbox.Message from legacy email.message.Message API to new EmailMessage API
Open
Nobody has claimed this yet.
3.8 (EOL)
stdlib
topic-email
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 32975 |
|---|---|
| Nosy | @warsaw, @bitdancer, @maxking |
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-03-01.05:44:18.590>
labels = ['type-feature', '3.8', 'expert-email']
title = 'mailbox: It would be nice to move mailbox.Message from legacy email.message.Message API to new EmailMessage API'
updated_at = <Date 2018-03-02.02:29:36.775>
user = 'https://github.com/maxking'
bugs.python.org fields:
activity = <Date 2018-03-02.02:29:36.775>
actor = 'maxking'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['email']
creation = <Date 2018-03-01.05:44:18.590>
creator = 'maxking'
dependencies = []
files = []
hgrepos = []
issue_num = 32975
keywords = []
message_count = 4.0
messages = ['313082', '313083', '313120', '313122']
nosy_count = 3.0
nosy_names = ['barry', 'r.david.murray', 'maxking']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue32975'
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 reading the mailbox.Message implementation and the email.message.EmailMessage API. The issue names no file or test path, so first map the current legacy API surface and its callers. Done means mailbox.Message uses the new EmailMessage API instead of email.message.Message, with affected behavior validated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100