pixi

+1 for Conda. I also have to mention pixi (https://github.com/prefix-dev/pixi) which kinda is a uv for the Conda ecosystem. Highly recommend!

> none of the docs really mention this Searching for the sister distro you mentioned, this[1] was one of the first links I stumbled upon, which included a link to the ARM ISO[2] and checksum[3] along with this note: > No homebrew, they don’t have arm builds, we will include Pixi[4] instead, which is a nice package manager built on the popular conda ecosystem - there’s some good stuff in there! [1] https://universal-blue.discourse.group/t/bluefin-lts-alpha-f... [2] https://download.projectbluefin.io/bluefin-lts-arm64.iso [3] https://download.projectbluefin.io/bluefin-lts-arm64.iso-CHE... [4] https://github.com/prefix-dev/pixi

Have you checked out https://github.com/prefix-dev/pixi? It's built by the folks who developed Mamba (a faster Conda implementation). It supports PyPI dependencies using UV, offers first-class support for multi-envs and lockfiles, and can be used to manage other system dependencies like CUDA. Their CLI also embraces much of the UX of UV and other modern dependency management tools in general.

same company has a different tool as well called pixi which aims for much nicer integration with the conda ecosystem. Also uses uv under the hood so speed is comparable. https://github.com/prefix-dev/pixi

> Please consider consolidating python dependency management instead of fragmenting it: https://github.com/mamba-org/mamba Mamba doesn't even interact with the official python packing ecosystem... It is purely a conda replacement and conda packaging is not Python packaging (it's a more fundamental fragmentation than choosing a particular tool). So weird choice to not fragment Python dependency management. If you depend on both conda and standard Python packaging (e.g. PyPI.org) you can use Pixi: https://github.com/prefix-dev/pixi?tab=readme-ov-file#pixi-p.... Pixi attempts to bridge the conda world and the Python package world, so it's possible to rely more deeply on standards based packaging but still use conda tooling when you need it.

For what it's worth, you can install pixi with Cargo. The current invocation is: cargo install --locked --git https://github.com/prefix-dev/pixi.git pixi I try new versions of pixi from time to time because I have a project that depends on LAVIS and EasyOCR. My default project-management tool, Poetry, has problems with PyTorch. Right now, I use pip-tools for the project. While Conda worked, I didn't like the tooling that much. What is currently blocking me from using pixi is the PyPI integration (https://github.com/prefix-dev/pixi/issues/1295). I can evaluate pixi in earnest when it is solved.

prefix-dev/pixi is a successor to Mamba and Conda which wraps libsolv like dnf. https://github.com/prefix-dev/pixi OpenSUSE/libsolv: https://github.com/openSUSE/libsolv OpenSUSE/zypper may have wrapped or may still wrap libsolv? TIL libsolv also supports arch .apk and .deb; there's a deb2solv utility to create libsolv .solv files: https://github.com/openSUSE/libsolv/blob/master/tools/deb2so... "[mamba-org/rattler:] A new memory-safe SAT solver for package management in Rust (port of libsolv)" (2024) https://prefix.dev/blog/the_new_rattler_resolver https://news.ycombinator.com/item?id=37101862 Pixi is integrating uv: https://github.com/astral-sh/uv/issues/1572#issuecomment-194... astral-sh/uv [1] solves versions with PubGrub [2], which was written for Dart: [1] https://github.com/astral-sh/uv [2] https://github.com/pubgrub-rs/pubgrub uv's

re: C/C++ development: anybody using conda/pixi for dependency management? Here's an example of compiling a C++ SDL program using pixi and the SDL dependency from conda-forge [1]. Seems viable as a replacement for things like vckpg [2] which only builds from source. I'm still researching this but it seems like rattler [3] is the tool to use to build/publish packages. The supported repos are: prefix.dev's own hosting, anaconda.org, artifactory or a self-hosted server. -- 1: https://github.com/prefix-dev/pixi/blob/main/examples/cpp-sd... 2: https://github.com/microsoft/vcpkg 3: https://prefix-dev.github.io/rattler-build/latest/authentica...

> I recently started using https://github.com/prefix-dev/pixi for Python projects Why is it based on the Conda ecosystem? Do you happen to know? I assume it's for portability, but that sounds heavy.

I recently started using https://github.com/prefix-dev/pixi for Python projects. I really love it so far, but this tool looks a bit more mature, which makes sense considering pixi is relatively new.

Isn't this basically what pixi wants to be? Wouldn't it be better to work together? https://github.com/prefix-dev/pixi/

(belated), but thanks for the `rtx` recommendation, I checked it out and it seems like "the right thing". Also keep an eye on the `pixi` tool which got some visibility here recently: https://github.com/prefix-dev/pixi

https://github.com/mamba-org/rattler : > Rattler: Rust crates for fast handling of conda packages https://github.com/prefix-dev/pixi : > https://pixi.sh/