python / python/cpython

mailbox : add option to prevent platform EOL conversion

Open
#74,597 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

3.7 (EOL) stdlib topic-email type-feature
Dominant language
Python
Stars
77.2k
Forks
36k
PR merge metrics
PR metrics pending

Description

BPO 30412
Nosy @bitdancer

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 2017-05-20.12:09:06.362>
labels = ['3.7', 'type-feature', 'library']
title = 'mailbox : add option to prevent platform EOL conversion'
updated_at = <Date 2017-05-21.18:25:15.801>
user = 'https://bugs.python.org/adder'

bugs.python.org fields:

activity = <Date 2017-05-21.18:25:15.801>
actor = 'r.david.murray'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2017-05-20.12:09:06.362>
creator = 'adder'
dependencies = []
files = []
hgrepos = []
issue_num = 30412
keywords = []
message_count = 2.0
messages = ['294028', '294108']
nosy_count = 2.0
nosy_names = ['r.david.murray', 'adder']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue30412'
versions = ['Python 3.7']

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.

Research direction

The issue identifies the mailbox library but names no implementation file or tests. Start by locating the mailbox implementation and its existing tests, then clarify which platform EOL conversions the option should prevent and how it should be exposed. Done means the requested option has defined behavior and is covered by 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
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.