_thread.interrupt_main() no longer interrupts Lock.wait

Open
#80,719 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
backend

Research direction

No source files or tests are named. Start by reviewing the linked BPO issue and the _thread.interrupt_main() and Lock.wait entry points to establish the expected interruption behavior; done means the regression is fixed and covered by a regression test.

Written by the indexing model from the issue text.

Description

3.8 (EOL) docs extension-modules stdlib type-bug
BPO 36538
Nosy @gpshead, @eryksun

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-04-05.20:07:07.889>
labels = ['extension-modules', '3.8', 'type-bug', 'library', 'docs']
title = '_thread.interrupt_main() no longer interrupts Lock.wait'
updated_at = <Date 2019-04-06.07:28:06.177>
user = 'https://github.com/gpshead'

bugs.python.org fields:

activity = <Date 2019-04-06.07:28:06.177>
actor = 'eryksun'
assignee = 'docs@python'
closed = False
closed_date = None
closer = None
components = ['Documentation', 'Extension Modules', 'Library (Lib)']
creation = <Date 2019-04-05.20:07:07.889>
creator = 'gregory.p.smith'
dependencies = []
files = []
hgrepos = []
issue_num = 36538
keywords = []
message_count = 2.0
messages = ['339518', '339528']
nosy_count = 3.0
nosy_names = ['gregory.p.smith', 'docs@python', 'eryksun']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue36538'
versions = ['Python 3.8']

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.