UnicodeEncodeError raise from smtplib.verify() method
Open
Nobody has claimed this yet.
3.7 (EOL)
3.8 (EOL)
stdlib
topic-email
topic-unicode
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 36093 |
|---|---|
| Nosy | @warsaw, @ezio-melotti, @Windsooon |
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 2019-02-23.07:59:18.247>
labels = ['3.8', 'type-bug', '3.7', 'expert-unicode']
title = 'UnicodeEncodeError raise from smtplib.verify() method'
updated_at = <Date 2020-03-27.11:16:23.501>
user = 'https://github.com/Windsooon'
bugs.python.org fields:
activity = <Date 2020-03-27.11:16:23.501>
actor = 'vstinner'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Unicode']
creation = <Date 2019-02-23.07:59:18.247>
creator = 'Windson Yang'
dependencies = []
files = []
hgrepos = []
issue_num = 36093
keywords = []
message_count = 4.0
messages = ['336374', '336375', '336509', '365140']
nosy_count = 3.0
nosy_names = ['barry', 'ezio.melotti', 'Windson Yang']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue36093'
versions = ['Python 3.6', 'Python 3.7', 'Python 3.8']
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
The issue identifies smtplib.verify() but no source file, test, reproduction, or expected behavior. Start by locating that entry point and reproducing the UnicodeEncodeError; the work is done when the intended Unicode input is handled without the reported exception and a regression test captures the behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100