DEBUGGING: Simultaneous stopping of all threads on breakpoint and switching between threads
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- devtools, operating-systems
Research direction
Start by reviewing the original BPO issue 21281 and the Python Interpreter Core context; the migrated issue names no files, tests, or entry points. Establish the intended thread-stopping and thread-switching behavior, then define tests that demonstrate both outcomes before considering implementation scope.
Written by the indexing model from the issue text.
Description
| BPO | 21281 |
|---|---|
| Nosy | @birkenfeld, @blueyed |
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 2014-04-17.08:52:07.323>
labels = ['interpreter-core', 'type-feature']
title = 'DEBUGGING: Simultaneous stopping of all threads on breakpoint and switching between threads'
updated_at = <Date 2019-04-27.04:51:18.040>
user = 'https://bugs.python.org/sjlnk'
bugs.python.org fields:
activity = <Date 2019-04-27.04:51:18.040>
actor = 'blueyed'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Interpreter Core']
creation = <Date 2014-04-17.08:52:07.323>
creator = 'sjlnk'
dependencies = []
files = []
hgrepos = []
issue_num = 21281
keywords = []
message_count = 2.0
messages = ['216677', '340967']
nosy_count = 3.0
nosy_names = ['georg.brandl', 'blueyed', 'sjlnk']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue21281'
versions = ['Python 3.5']
- 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
-
area/auth bug comp/agent P3 platform/discord type/security
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
NousResearch/hermes-agent#117848 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100