mbox parser incorrect behaviour

Open
#55,937 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
backend

Research direction

The issue concerns incorrect behaviour in the mbox parser within Python's email library, but names no file, test, or reproduction. Start by reviewing the migrated BPO issue 11728 and the email-library parser entry points; done requires a specific reproducible failure and a regression test.

Written by the indexing model from the issue text.

Description

3.10 3.8 (EOL) 3.9 (EOL) stdlib topic-email type-bug
BPO 11728
Nosy @warsaw, @bitdancer, @akheron

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 2011-03-31.12:04:25.847>
labels = ['type-bug', '3.8', 'expert-email', '3.10', 'library', '3.9']
title = 'mbox parser incorrect behaviour'
updated_at = <Date 2020-11-10.18:18:35.131>
user = 'https://bugs.python.org/wally1980'

bugs.python.org fields:

activity = <Date 2020-11-10.18:18:35.131>
actor = 'iritkatriel'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)', 'email']
creation = <Date 2011-03-31.12:04:25.847>
creator = 'wally1980'
dependencies = []
files = []
hgrepos = []
issue_num = 11728
keywords = []
message_count = 8.0
messages = ['132657', '132671', '132687', '138245', '163812', '163872', '163902', '164636']
nosy_count = 5.0
nosy_names = ['barry', 'r.david.murray', 'sdaoden', 'wally1980', 'petri.lehtinen']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue11728'
versions = ['Python 3.8', 'Python 3.9', 'Python 3.10']

Dominant language
Python
Stars
77.2k
Forks
36k
Avg merge
1d 9h
Merged PRs (30d)
558

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from python/cpython

All issues in python/cpython

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.