Reason for pybind11 run export?

[matthewfeickert]

Comment:

👋 @conda-forge/xtensor-python I see that you have a run export on pybind11

xtensor-python-feedstock/recipe/recipe.yaml

Line 40 in cc77407

- ${{ pin_compatible('pybind11', upper_bound='x') }}

and I think this is causing build issues for linux-aarch64 that have dependencies on xtensor-python (c.f. conda-forge/simsopt-feedstock#1 (comment)). Why do you have a run export on a build tool?

edit: Asked on conda-forge Zulip too. #general > Reasons for a run export on pybind11?

[matthewfeickert]

From @chrisburr:

xtensor-python is a head-only library, see the file list in https://conda-metadata-app.streamlit.app/?q=conda-forge%2Flinux-64%2Fxtensor-python-0.29.0-np2py314h27e5287_1.conda

and it actually depends on pybind11 directly: https://github.com/xtensor-stack/xtensor-python/blob/3cc25f4c7531c29b1869a4e46a39c3e89d391984/include/xtensor-python/xtensor_type_caster_base.hpp#L20.

I don’t think there is any reason for pin_compatible. It should just have an appropriate version constraint. There is no relation between host and run versions of pybind11 as it’s not actually building anything in the feedstock.

[JohanMabille]

I think this is a leftover when the host dependency on pybind11 was stricter (i.e. >=2.12, <3), and we tohught that upgrading to pybind 3 would lead to new bounds (i.e. >=3,<4). But indeed it is not the correct approach since we don't build anything in this feedstock (technically we could even remove the dependency from the host section, but let's keep it for the day we decide to build the tests).