Add a datatype to represent mime types to the email module

Open
#63,479 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start by reading the email module and the original BPO issue 19280 linked in the report, since no source file or test is identified. Determine the intended datatype's scope and integration points from that discussion; the work is done when the email module represents MIME types with the agreed behavior and suitable coverage.

Written by the indexing model from the issue text.

Description

easy stdlib topic-email type-feature
BPO 19280
Nosy @warsaw, @pitrou, @ezio-melotti, @bitdancer, @vadmium

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 2013-10-17.14:13:03.506>
labels = ['easy', 'type-feature', 'expert-email']
title = 'Add a datatype to represent mime types to the email module'
updated_at = <Date 2014-09-05.23:52:54.511>
user = 'https://github.com/bitdancer'

bugs.python.org fields:

activity = <Date 2014-09-05.23:52:54.511>
actor = 'martin.panter'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['email']
creation = <Date 2013-10-17.14:13:03.506>
creator = 'r.david.murray'
dependencies = []
files = []
hgrepos = []
issue_num = 19280
keywords = ['easy']
message_count = 3.0
messages = ['200128', '200265', '200638']
nosy_count = 5.0
nosy_names = ['barry', 'pitrou', 'ezio.melotti', 'r.david.murray', 'martin.panter']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue19280'
versions = ['Python 3.5']

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.