email.utils.formataddr does not respect double spaces
Open
Nobody has claimed this yet.
stdlib
topic-email
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 47244 |
|---|---|
| Nosy | @warsaw, @bitdancer, @AlecRosenbaum |
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 2022-04-06.17:45:12.930>
labels = ['type-bug', '3.8', 'expert-email', '3.10', '3.11', '3.7', '3.9']
title = 'email.utils.formataddr does not respect double spaces'
updated_at = <Date 2022-04-06.17:45:12.930>
user = 'https://github.com/AlecRosenbaum'
bugs.python.org fields:
activity = <Date 2022-04-06.17:45:12.930>
actor = 'AlecRosenbaum'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['email']
creation = <Date 2022-04-06.17:45:12.930>
creator = 'AlecRosenbaum'
dependencies = []
files = []
hgrepos = []
issue_num = 47244
keywords = []
message_count = 1.0
messages = ['416891']
nosy_count = 3.0
nosy_names = ['barry', 'r.david.murray', 'AlecRosenbaum']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue47244'
versions = ['Python 3.7', 'Python 3.8', 'Python 3.9', 'Python 3.10', 'Python 3.11']
Linked PRs
- gh-92638
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
Review linked PR gh-92638 and the migrated issue details first; this issue names no source file or test. Confirm whether the double-space behavior is already addressed there, using email.utils.formataddr's expected formatting as the completion criterion.
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
- Needs clarification
- Newbie friendliness
- 25/100