pybind/pybind11
1
0
Fork 0
mirror of https://github.com/pybind/pybind11.git synced 2026-03-14 20:27:47 +00:00
Code Issues Packages Projects Releases Wiki Activity

[skip ci] Explain: conduit feature only covers from-Python-to-C++ conversions (#5740)

Browse Source
This commit is contained in:
Ralf W. Grosse-Kunstleve
2025-06-20 13:23:26 -07:00
committed by GitHub
parent 03d8f48750
commit 4dc4aca2e1
2 changed files with 7 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
include/pybind11/conduit/pybind11_conduit_v1.h
View File

@@ -6,6 +6,11 @@
* including pybind11 versions with different PYBIND11_INTERNALS_VERSION's.
* NOTE: The conduit feature
only covers from-Python-to-C++ conversions, it
does not cover from-C++-to-Python conversions.
(For the latter, a different feature would have to be added.)
The naming of the feature is a bit misleading:
* The feature is in no way tied to pybind11 internals.

4
tests/test_cpp_conduit.py
View File

@@ -151,8 +151,8 @@ def test_exo_planet_c_api_premium_traveler(premium_traveler_type):
def test_home_planet_wrap_very_lonely_traveler():
# This does not exercise the cpp_conduit feature, but is here to
# demonstrate that the cpp_conduit feature does not solve all
# cross-extension interoperability issues.
# demonstrate that the cpp_conduit feature does not solve
# cross-extension base-and-derived class interoperability issues.
# Here is the proof that the following works for extensions with
# matching `PYBIND11_INTERNALS_ID`s:
# test_cpp_conduit.cpp: