EmailMessage should support Header objects

Open
#65,294 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

The issue names EmailMessage but provides no file or test path. Start by locating the email package's EmailMessage entry point and checking how header values are handled. Done means Header objects are accepted without breaking existing header behavior, with tests covering the new support.

Written by the indexing model from the issue text.

Description

stdlib topic-email
BPO 21095
Nosy @warsaw, @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 2014-03-29.03:33:26.217>
labels = ['expert-email']
title = 'EmailMessage should support Header objects'
updated_at = <Date 2019-03-15.23:14:34.606>
user = 'https://bugs.python.org/brandon-rhodes'

bugs.python.org fields:

activity = <Date 2019-03-15.23:14:34.606>
actor = 'BreamoreBoy'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['email']
creation = <Date 2014-03-29.03:33:26.217>
creator = 'brandon-rhodes'
dependencies = []
files = []
hgrepos = []
issue_num = 21095
keywords = []
message_count = 3.0
messages = ['215112', '220637', '220646']
nosy_count = 3.0
nosy_names = ['barry', 'r.david.murray', 'brandon-rhodes']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = None
url = 'https://bugs.python.org/issue21095'
versions = ['Python 3.4']

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.