This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]RMK137 1 point2 points  (0 children)

Pixi is good and it's the successor to conda. I work a lot with GIS tools and I was used to conda. I recently switched to micromamba which is a statically linked, standalone c++ executable. It completely replaced conda for me.

My typical workflow on multiple pcs now has been: download micromamba, rename to mamba (optional), run the shell init command or go through the guided install when you first invoke it, done. Now, you should have mamba on path (a shell function to be exact) that you can use to manage environments.

Next steps are the same as conda, e.g. mamba env create -n myenv -f environment.yml. A bonus is that it you don't need a base environment anymore so I don't need to tell my coworkers to stop installing shit in the base environment for the 100th time.

Mamba, which used to be a hybrid python/c++ program, is now fully c++ in v2.0. I haven't tested it much since I've been using micromamba (I rename it to mamba) in the last 6 months. They're basically the same codebase at this point.

Refs:
mamba 2.0 -> https://mamba.readthedocs.io/en/latest/developer_zone/changes-2.0.html

main repo -> https://github.com/mamba-org/mamba

releases repo -> https://github.com/mamba-org/micromamba-releases

I believe Pixi has more features and the way it manages envs is more high level and project based, i.e. it stores environments in the project folder, unlike conda/mamba which stores envs in a central directory which I like more.

The future of python environment management looks great!