Rare dead-lock observed when using `set_num_threads()` in parallel environment

Open
#571 1 comment 0 reactions 0 assignees View on GitHub

@kif is already working on this.

Since Sep 27, 2026.

  • #572 by @kif — open

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

  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 pydata/numexpr

All issues in pydata/numexpr

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.