email.utils.encode_rfc2231(string, None, None) returns broken value
Open
Nobody has claimed this yet.
3.15
stdlib
topic-email
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 40837 |
|---|---|
| Nosy | @warsaw, @orsenthil, @bitdancer, @maxking, @spaceone |
| PRs |
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 2020-06-01.02:17:05.810>
labels = ['type-bug', 'library', 'expert-email', '3.10']
title = 'email.utils.encode_rfc2231(string, None, None) returns broken value'
updated_at = <Date 2020-06-05.04:08:13.869>
user = 'https://github.com/spaceone'
bugs.python.org fields:
activity = <Date 2020-06-05.04:08:13.869>
actor = 'xtreak'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)', 'email']
creation = <Date 2020-06-01.02:17:05.810>
creator = 'spaceone'
dependencies = []
files = []
hgrepos = []
issue_num = 40837
keywords = []
message_count = 2.0
messages = ['370526', '370670']
nosy_count = 5.0
nosy_names = ['barry', 'orsenthil', 'r.david.murray', 'maxking', 'spaceone']
pr_nums = ['20564']
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue40837'
versions = ['Python 3.10']
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the email.utils.encode_rfc2231(string, None, None) entry point and review PR #20564 for the existing attempted fix. Confirm the intended return value from BPO issue 40837, then add or update regression coverage and validate the email library tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100