Tkinter single-threaded deadlock

Open
#58,598 11 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
desktop

Research direction

Start by examining deadlocktest-0.2.tar.gz, then review reentrant-tkinter.patch alongside its source, tests, and documentation changes. Reproduce the Tkinter single-threaded deadlock and determine whether the proposed patch addresses it; done should include verified behavior and corresponding tests and docs.

Written by the indexing model from the issue text.

Description

3.10 3.8 (EOL) 3.9 (EOL) stdlib topic-tkinter type-bug
BPO 14390
Nosy @ned-deily, @bitdancer, @asvetlov
Files
  • deadlocktest-0.2.tar.gz: Tarball of a standalone test exhibiting the faulty behavior
  • reentrant-tkinter.patch: Patch for source, tests, and docs
  • 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 2012-03-22.20:48:30.561>
    labels = ['3.8', 'type-bug', 'expert-tkinter', '3.9', '3.10']
    title = 'Tkinter single-threaded deadlock'
    updated_at = <Date 2020-11-16.00:04:57.129>
    user = 'https://bugs.python.org/jcbollinger'
    

    bugs.python.org fields:

    activity = <Date 2020-11-16.00:04:57.129>
    actor = 'iritkatriel'
    assignee = 'none'
    closed = False
    closed_date = None
    closer = None
    components = ['Tkinter']
    creation = <Date 2012-03-22.20:48:30.561>
    creator = 'jcbollinger'
    dependencies = []
    files = ['25032', '25866']
    hgrepos = []
    issue_num = 14390
    keywords = ['patch']
    message_count = 11.0
    messages = ['156619', '156768', '156861', '156924', '156927', '156942', '156943', '162536', '162539', '162542', '162547']
    nosy_count = 5.0
    nosy_names = ['ned.deily', 'jnoller', 'r.david.murray', 'asvetlov', 'jcbollinger']
    pr_nums = []
    priority = 'normal'
    resolution = None
    stage = 'patch review'
    status = 'open'
    superseder = None
    type = 'behavior'
    url = 'https://bugs.python.org/issue14390'
    versions = ['Python 3.8', 'Python 3.9', 'Python 3.10']
    

    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.