pybind / pybind/pybind11

[BUG]: Can't use PYBIND11_NUMPY_DTYPE with subinterpreters

Open
#5,781 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

triage
Dominant language
C++
Stars
18k
Forks
2.3k
Avg merge
5d 17h
Merged PRs (30d)
10

Description

Required prerequisites
What version (or hash if on master) of pybind11 are you using?

3.0.0

Problem description

Registering a DTYPE fails in subinterpreters because the DTYPE is already registered. Any thoughts on how to make this subinterpreter safe?

ImportError: NumPy: dtype is already registered

Edit: I think numpy may not work in subinterpreters; if I suppress this error when it's already loaded, then it looks like numpy throws an error when importing. So it might not be very important to solve until numpy supports subinterpreters.

Reproducible example code
PYBIND11_NUMPY_DTYPE(weighted_sum, value, variance);
Is this a regression? Put the last known working version here if it is.

Not a regression

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.

Research direction

Start with the PYBIND11_NUMPY_DTYPE(weighted_sum, value, variance) example and reproduce it across subinterpreters. Investigate whether the failure comes from pybind11's dtype registration or NumPy's subinterpreter support; done requires a confirmed safe behavior or a documented blocker.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, numpy, python
Domain
backend-api-design
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.