No reliable clean shutdown method
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
Research direction
The issue names no source file, test, or entry point; begin by reading the linked BPO issue 33087 and its discussion. Clarify the intended Python library API and shutdown semantics, then determine what tests would demonstrate a reliable clean shutdown.
Written by the indexing model from the issue text.
Description
| BPO | 33087 |
|---|---|
| Nosy | @MojoVampire, @Void2258 |
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 2018-03-16.17:44:07.261>
labels = ['3.8', 'type-feature', 'library']
title = 'No reliable clean shutdown method'
updated_at = <Date 2018-03-20.00:19:56.780>
user = 'https://github.com/Void2258'
bugs.python.org fields:
activity = <Date 2018-03-20.00:19:56.780>
actor = 'brett.cannon'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2018-03-16.17:44:07.261>
creator = 'Void2258'
dependencies = []
files = []
hgrepos = []
issue_num = 33087
keywords = []
message_count = 2.0
messages = ['313961', '313969']
nosy_count = 2.0
nosy_names = ['josh.r', 'Void2258']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue33087'
versions = ['Python 3.8']
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
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.
More from python/cpython
-
docs pending
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
build type-bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
stdlib topic-email type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
🐛 Bug 🔔 Pending processing
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
jumpserver/jumpserver#17584 ·