Skip to content

Explain: conduit feature only covers from-Python-to-C++ conversions #5740

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 20, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions include/pybind11/conduit/pybind11_conduit_v1.h
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down
4 changes: 2 additions & 2 deletions tests/test_cpp_conduit.py
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down