> particularly because it also allows for non-Python dependencies (one of my recent projects involved a browser automation solution, and I chose to install Fire

> particularly because it also allows for non-Python dependencies (one of my recent projects involved a browser automation solution, and I chose to install Firefox in a conda env You could just as well install it either globally with pixi global, or as a project dependency in a pixi project. In this case, the latter. > I also have a few shared envs, for quick tests Fair, I just use temporary directories with pixi projects for that and thus no longer see a point in conda envs for this. It has the added benefit that all my temporary directories are in the same location and easy to get rid of. > general utils I would want those to be available at all times, so conda envs aren't fit for that purpose. Instead, I use pixi's global subcommand. > Poetry for project management. That limits you to lock files for python dependencies only, unfortunately. In a project relying on browser automation, I would want the browser version to be recorded in the lock file as well. Pixi does that. --- I still don't really see why you found pixi lacking. It addresses all of your problems, maybe with the exception of globally installing multiple and non-CLI packages. But again, conda isn't any better as you are generally advised not to install stuff into the base env and conda has no other facility for globally installing general utilities.