Rare dead-lock observed when using `set_num_threads()` in parallel environment
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- python
- Domain
- performance
Research direction
Start with the set_num_threads() entry point and the parallel test execution described here, reproducing the deadlock on a free-threaded Python build. Compare the behavior with the investigation in issue #569; done means the rare deadlock is understood, prevented, and covered by a regression test.
Written by the indexing model from the issue text.
Description
Much more common on free-threaded versions of python.
This has been found while tinkering around parallel execution of tests with such python environment in issue #569, but it is apparently unrelated.
- Dominant language
- Python
- Stars
- 2.5k
- Forks
- 235
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 pydata/numexpr
-
Error in numexpr.validate documentationPossibly taken @syahra712 claimed this 40 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Python 3.15 wheelsOpen
Difficulty 2/5 1-3 hours Newbie friendliness 50/100
-
Heap corruption when a compiled NumExpr object is called from several threads with NUMEXPR_NUM_THREADS=1Possibly taken @xuu33030 claimed this 62 days ago. OpenStale
Difficulty 4/5 3-5 days Newbie friendliness 50/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
abetlen/llama-cpp-python#2424 ·
Maintainers usually reply within 1 day
-
Bug IronPython Python 3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
pyrevitlabs/pyRevit#4184 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 74/100
jqueryscript/awesome-claude-code#1009 ·
-
tests
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day