mailbox.mbox fails on non ASCII characters
Open
Nobody has claimed this yet.
3.10
topic-email
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 42433 |
|---|---|
| Nosy | @warsaw, @terryjreedy, @bitdancer, @flokli |
| PRs |
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-11-22.10:09:32.634>
labels = ['type-feature', 'expert-email', '3.10']
title = 'mailbox.mbox fails on non ASCII characters'
updated_at = <Date 2020-12-05.20:44:11.920>
user = 'https://github.com/flokli'
bugs.python.org fields:
activity = <Date 2020-12-05.20:44:11.920>
actor = 'terry.reedy'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['email']
creation = <Date 2020-11-22.10:09:32.634>
creator = 'flokli'
dependencies = []
files = []
hgrepos = []
issue_num = 42433
keywords = ['patch']
message_count = 8.0
messages = ['381607', '381627', '381637', '381975', '382052', '382169', '382581', '382584']
nosy_count = 4.0
nosy_names = ['barry', 'terry.reedy', 'r.david.murray', 'flokli']
pr_nums = ['23553']
priority = 'normal'
resolution = None
stage = 'patch review'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue42433'
versions = ['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
Review PR #23553 and the migrated BPO details first; the issue identifies mailbox.mbox and the email component but names no source file or test. Confirm the reported non-ASCII failure and establish the expected behavior before changing it; done means the mailbox.mbox case is resolved and covered by an appropriate test.
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
- Needs clarification
- Newbie friendliness
- 15/100