mailbox fails to read message from mbox
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 | 45882 |
|---|
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 2021-11-23.18:18:02.343>
labels = ['3.8', 'type-bug', 'library']
title = 'mailbox fails to read message from mbox'
updated_at = <Date 2021-11-23.18:18:02.343>
user = 'https://bugs.python.org/peterwurmsdobler'
bugs.python.org fields:
activity = <Date 2021-11-23.18:18:02.343>
actor = 'peter.wurmsdobler'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2021-11-23.18:18:02.343>
creator = 'peter.wurmsdobler'
dependencies = []
files = []
hgrepos = []
issue_num = 45882
keywords = []
message_count = 1.0
messages = ['406873']
nosy_count = 1.0
nosy_names = ['peter.wurmsdobler']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue45882'
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
No source file, test, reproduction, or expected behavior is provided in the migrated issue. Start by reviewing the linked BPO issue 45882, then locate the mailbox handling entry point and reproduce the failure with an mbox message. Done means mailbox can read the affected message and a regression test covers the behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100