sched.py: run() is caught in delayfunc even if all events are cancelled.
Open
Nobody has claimed this yet.
stdlib
type-feature
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 37174 |
|---|---|
| Nosy | @tim-one, @rhettinger, @terryjreedy, @ernestum |
| 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 2019-06-06.12:06:26.419>
labels = ['type-feature', 'library', '3.9']
title = 'sched.py: run() is caught in delayfunc even if all events are cancelled.'
updated_at = <Date 2019-06-08.05:49:36.784>
user = 'https://github.com/ernestum'
bugs.python.org fields:
activity = <Date 2019-06-08.05:49:36.784>
actor = 'rhettinger'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2019-06-06.12:06:26.419>
creator = 'ernestum'
dependencies = []
files = []
hgrepos = []
issue_num = 37174
keywords = []
message_count = 3.0
messages = ['344804', '345021', '345023']
nosy_count = 4.0
nosy_names = ['tim.peters', 'rhettinger', 'terry.reedy', 'ernestum']
pr_nums = ['13862']
priority = 'normal'
resolution = None
stage = 'test needed'
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue37174'
versions = ['Python 3.9']
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 in sched.py at the run() entry point and review PR 13862, which is referenced by the issue. Verify the behavior when all scheduled events are cancelled: run() should not remain caught in delayfunc after cancellation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100