EmailMessage should throw an error if policy is set to compat32

Open
#69,826 6 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
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
backend

Research direction

Start by locating EmailMessage and the email component's policy handling, then read the linked BPO issue and its six-message discussion for the intended compat32 behavior. Identify the expected error and add regression coverage; done means EmailMessage rejects a compat32 policy consistently.

Written by the indexing model from the issue text.

Description

stdlib topic-email type-bug
BPO 25640
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 2015-11-16.21:48:00.592>
labels = ['type-bug', 'expert-email']
title = 'EmailMessage should throw an error if policy is set to compat32'
updated_at = <Date 2018-07-11.07:41:35.827>
user = 'https://bugs.python.org/MatthieuPepin'

bugs.python.org fields:

activity = <Date 2018-07-11.07:41:35.827>
actor = 'serhiy.storchaka'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['email']
creation = <Date 2015-11-16.21:48:00.592>
creator = 'Matthieu Pepin'
dependencies = []
files = []
hgrepos = []
issue_num = 25640
keywords = []
message_count = 6.0
messages = ['254757', '254758', '254759', '254765', '254766', '254769']
nosy_count = 3.0
nosy_names = ['barry', 'r.david.murray', 'Matthieu Pepin']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue25640'
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.