sched.py: run() is caught in delayfunc even if all events are cancelled.

Open
#81,355 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
backend

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.

Description

stdlib type-feature
BPO 37174
Nosy @tim-one, @rhettinger, @terryjreedy, @ernestum
PRs
  • python/cpython#13862
    		•

    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']

    Dominant language
    Python
    Stars
    77.2k
    Forks
    36k
    Avg merge
    1d 9h
    Merged PRs (30d)
    558

    Contributor guide

    Open the contributing guide

    First steps

    1. Read the whole issue, then the project's contributing guide.
    2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
    3. Fork the repository and make your change on a branch.
    4. Open a pull request that references the issue number.

    More from python/cpython

    All issues in python/cpython

    Similar issues

    More Python issues

    Get new issues in your inbox

    A short digest of beginner-friendly GitHub issues.