email.parser.BytesParser failed to parse mail when it is with BOM
Open
Nobody has claimed this yet.
3.9 (EOL)
stdlib
topic-email
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 43530 |
|---|---|
| Nosy | @tzing |
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-03-17.15:45:56.464>
labels = ['type-bug', 'library', '3.9']
title = 'email.parser.BytesParser failed to parse mail when it is with BOM'
updated_at = <Date 2021-03-17.15:45:56.464>
user = 'https://github.com/tzing'
bugs.python.org fields:
activity = <Date 2021-03-17.15:45:56.464>
actor = 'tzing'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2021-03-17.15:45:56.464>
creator = 'tzing'
dependencies = []
files = []
hgrepos = []
issue_num = 43530
keywords = []
message_count = 1.0
messages = ['388929']
nosy_count = 1.0
nosy_names = ['tzing']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue43530'
versions = ['Python 3.9']
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 at Python's email.parser.BytesParser and reproduce the reported failure with a mail containing a BOM, using the Python 3.9 context given in the issue. Identify the relevant library file and add or update a regression test showing that the BOM-containing message parses successfully; done means the test passes without breaking existing parser behavior.
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
- 30/100