[BUG]: pybind11 return numpy array by copy instead of reference.
Open
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
- Make sure you've read the documentation. Your issue may be addressed there.
- Search the issue tracker and Discussions to verify that this hasn't already been reported. +1 or comment there if it has.
- Consider asking first in the Gitter chat room or in a Discussion.
What version (or hash if on master) of pybind11 are you using?
2.11
Problem description
py::array_t<float> return_from_cpp()
{
float* data = new float[5];
printf("data ptr: %ld", data);
return py::array_t<float>({1, 5}, data);
}
I want to return an existing data in c++ to python, so I try build a py::array_t<float> object by pointer.
But python receive a copy array.
So what should I do?
Reproducible example code
c++
py::array_t<float> return_from_cpp()
{
float* data = new float[5];
printf("data ptr: %ld", data);
return py::array_t<float>({1, 5}, data);
}
from package import return_from_cpp
data = return_from_cpp()
print(data.ctypes.data)
### Is this a regression? Put the last known working version here if it is.
Not a regression
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.
Research direction
Reproduce the reported C++ return_from_cpp example and compare the pointer printed in C++ with Python's data.ctypes.data. Investigate py::array_t construction from an existing pointer and establish the expected reference or ownership behavior; no project files or tests are named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, numpy, python
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100