You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Assuming this is, in fact, true, we plan to globally pin the version of pybind11 for all of conda-forge. See conda-forge/conda-forge-pinning-feedstock#849. This will ease the maintenance burden for users who want to use different packages together and don't want to run around updating pins in recipes.
cc @conda-forge/core @conda-forge/pybind11
The text was updated successfully, but these errors were encountered:
This should only change when the internal ABI string changes. The string last changed for 2.4, I believe. Also, keep in mind that many (most?) packages internally pin pybind11, by submodule (in git) and including the headers in the SDist.
Issue:
Environment (
conda list
):Details about
conda
and system (conda info
):We got a report from @bluescarni (see conda-forge/conda-forge-pinning-feedstock#849 (comment)) that different pybind11 versions generate python libraries which are not interoperable between one another.
Assuming this is, in fact, true, we plan to globally pin the version of pybind11 for all of conda-forge. See conda-forge/conda-forge-pinning-feedstock#849. This will ease the maintenance burden for users who want to use different packages together and don't want to run around updating pins in recipes.
cc @conda-forge/core @conda-forge/pybind11
The text was updated successfully, but these errors were encountered: