6 ms·
Conda manages binaries and their native dependencies together, including shared libraries[0]. This offers significant advantages over uv and pip when distributi
by phronimos 1y ago
Conda manages binaries and their native dependencies together, including shared libraries[0]. This offers significant advantages over uv and pip when distributing packages with C extensions, such as dependency resolution that accounts for shared library requirements, and better package isolation.
[0]: https://docs.conda.io/projects/conda-build/en/latest/resources/use-shared-libraries.html https://docs.conda.io/projects/conda-build/en/latest/resourc...
- reedf1 1y agoUse PDM with the UV backend - this accomplishes this in a much more lightweight and performant way.
- aeroevan 1y agoDoes PDM manage C/Fortran library dependencies? IIRC conda was the only solution for managing both native and python dependencies but I haven't really looked elsewhere. With wheels and the manylinux specifications there's less of a usecase for that, but still could be useful
- reedf1 1y agoNot sure about Fortran - but C for sure, yes.
- jaimergp 1y agoWhere does it fetch the C packages from? I always thought PDM was a _Python_ package manager, so the only source is PyPI or another index.
- oblvious-earth 1y agoPDM has plugins, such as being able to invoke conda commands: https://github.com/pdm-project/awesome-pdm https://github.com/pdm-project/awesome-pdm Otherwise I don't know what they're talking about, it is indeed a Python package manager.
- agoose77 1y agoThe PyPI ecosystem can not, for the foreseeable future, replicate the scope of the conda ecosystem. From microarch builds to library deduplication, conda is a more general purpose solution. That doesn't mean that one "wins out" (and, for reference I predominantly use Python's PyPI), but they're not the same tools.