While PyPI can host also non-Python dependencies (and it does, see for example the cmeel C++ distribution on PyPI, https://pypi.org/search/?q=cmeel-*), I am not sure how it can scale to handle ABI migrations without a centralized tooling.
Comments
Log in with your Bluesky account to leave a comment
For example, Julia package manager started effectively to package non-Julia dependencies for its packages, but it adopted an extremely centralized model with https://github.com/JuliaPackaging/Yggdrasil that seems quite different from the distributed model of how PyPI wheels are built as of late 2024.
I can only re-iterate that this is not a technical problem but a social one. Long before we can discuss tooling there would need to be the demand to have that in the first place. Today that demand is met by Conda, so there is not enough pressure to solve it on PyPI. I expect this to change.
I completely agree on this being a social problem (and on social problems being harder to solve then tech ones). Why do you think there will be an increase of pressure on PyPI to solve those problems, if the demand is already met by conda-forge ?
Comments