[Subinterpreters] Interrupts are not propagated from python to c++ side
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
No files, tests, or entry points are named. Start by locating the subinterpreter execution path and the signal-handling path, then compare how the main interpreter handles interrupts. Done means interrupts raised during subinterpreter execution are propagated to the C++ side.
Written by the indexing model from the issue text.
Description
Subinterpreters don't handle interrupts when they are in execution (see cpython issue 113130). The main interpreter is the only one which performs signal handling.
- Dominant language
- C++
- Stars
- 3
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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 domferr/fastflow-python
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 20/100
domferr/fastflow-python#10 ·
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 15/100
All issues in domferr/fastflow-python
Similar issues
-
bug build
Difficulty 1/5 Under an hour Newbie friendliness 91/100
facebookincubator/velox#19194 ·
-
JIT-compiled number -> Decimal conversion silently overflows instead of raising DECIMAL_OVERFLOW Openfuzz
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
ClickHouse/ClickHouse#122114 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
module/agent platform/macos type/bug/regression
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
enhancement PyCDE
Difficulty 2/5 1-3 hours Newbie friendliness 78/100