Certificate verification errors in urllib.request become URLError
Open
Nobody has claimed this yet.
3.10
3.8 (EOL)
3.9 (EOL)
stdlib
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 36866 |
|---|---|
| Nosy | @ned-deily, @sivel |
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-05-09.15:48:32.609>
labels = ['3.8', 'type-bug', 'library', '3.9', '3.10']
title = 'Certificate verification errors in urllib.request become URLError'
updated_at = <Date 2021-04-17.19:34:44.278>
user = 'https://github.com/sivel'
bugs.python.org fields:
activity = <Date 2021-04-17.19:34:44.278>
actor = 'christian.heimes'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2019-05-09.15:48:32.609>
creator = 'sivel'
dependencies = []
files = []
hgrepos = []
issue_num = 36866
keywords = []
message_count = 3.0
messages = ['341985', '342200', '342204']
nosy_count = 2.0
nosy_names = ['ned.deily', 'sivel']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue36866'
versions = ['Python 3.8', 'Python 3.9', '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 with the urllib.request certificate-verification error path and review the linked BPO issue 36866 and its three historical messages. Determine the intended exception behavior and identify the relevant library tests; done means certificate verification errors behave as specified without regressing existing urllib.request coverage.
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
- 30/100