email package content-transfer-encoding behaviour changed

Open
#43,702 12 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
Needs clarification
Activity status
Quiet
Tech stack
python
Domain
backend, documentation

Research direction

Start by reviewing the migrated BPO discussion for the email package and the Documentation and Library (Lib) components; no source file or test is named in the issue. Clarify which content-transfer-encoding behavior changed and whether the intended result is a documentation update or a code correction, then verify the chosen behavior against the relevant email-package documentation or tests.

Written by the indexing model from the issue text.

Description

3.10 3.11 3.9 (EOL) stdlib topic-email type-bug
BPO 1525919
Nosy @warsaw, @bitdancer, @iritkatriel

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 2006-07-20.14:22:21.000>
labels = ['type-bug', 'expert-email', '3.10', '3.11', '3.9', 'library', 'docs']
title = 'email package content-transfer-encoding behaviour changed'
updated_at = <Date 2021-12-13.09:55:31.268>
user = 'https://bugs.python.org/ThomasAH'

bugs.python.org fields:

activity = <Date 2021-12-13.09:55:31.268>
actor = 'iritkatriel'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation', 'Library (Lib)', 'email']
creation = <Date 2006-07-20.14:22:21.000>
creator = 'ThomasAH'
dependencies = []
files = []
hgrepos = []
issue_num = 1525919
keywords = []
message_count = 11.0
messages = ['29229', '29230', '58248', '73949', '105045', '184663', '184685', '184692', '184698', '408387', '408433']
nosy_count = 9.0
nosy_names = ['barry', 'ThomasAH', 'rdemetrescu', 'paulproteus', 'r.david.murray', 'docs@python', 'python-dev', 'littleq0903', 'iritkatriel']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue1525919'
versions = ['Python 3.9', 'Python 3.10', 'Python 3.11']

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.