mailbox: Implement >From_ decoding on input from mbox
Open
Nobody has claimed this yet.
stdlib
topic-email
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 29053 |
|---|---|
| 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-12-23.14:16:48.385>
labels = ['type-feature', 'expert-email']
title = 'mailbox: Implement >From_ decoding on input from mbox'
updated_at = <Date 2017-01-03.12:21:51.618>
user = 'https://bugs.python.org/bpoaugust'
bugs.python.org fields:
activity = <Date 2017-01-03.12:21:51.618>
actor = 'vstinner'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['email']
creation = <Date 2016-12-23.14:16:48.385>
creator = 'bpoaugust'
dependencies = []
files = ['46017']
hgrepos = []
issue_num = 29053
keywords = []
message_count = 5.0
messages = ['283879', '283882', '283883', '283914', '284500']
nosy_count = 3.0
nosy_names = ['barry', 'r.david.murray', 'bpoaugust']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue29053'
versions = ['Python 3.5']
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 with the referenced mboxo_patch.py and the mailbox issue context in BPO 29053. Determine the expected >From_ decoding behavior for mbox input, then verify that the implementation handles it consistently and that the resulting behavior is covered by the relevant mailbox tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100