multiversion VS nix-cde

I don't see much other than reliance on sys.modules keying that is a hindrance in a better import story, and even that is solvable. Already 12 years ago I showed that loading multiple incompatible versions of a library into the same Python interpreter is possible, and that was a long time before importlib landed which would make some of this easier.

This is what I'm using with gitlab: https://github.com/takeda/nix-cde/blob/master/contrib/gitlab...

I myself use https://github.com/takeda/nix-cde it just wraps other projects in an opinionated way and contains the boiler plate that I would normally use otherwise.

There's a project that does this with using Nix: https://github.com/takeda/nix-cde (this is a wrapper around https://github.com/nix-community/poetry2nix)

I personally use this: https://github.com/takeda/nix-cde it has the benefit of a reproducible build environment, but unfortunately anything involving Nix has a steep learning curve.

I use this myself: https://github.com/takeda/nix-cde

I don't use NixOS myself, but have Nix installed on my Mac, and it seems to provide all functionality of package or version managers I needed.

I think though it is more complex because it is a programming language that provides this functionality instead of purpose build tool like asdf.

For my needs I created a framework for development: https://github.com/takeda/nix-cde to avoid cruft of including the same things over and over in my projects.

Not an OP, but I became a big fan of using poetry for managing dependencies. For managing python version I started using Nix package manager. It allows to describe all dependencies via code, but with time that code became a boilerplate, so I created this: https://github.com/takeda/nix-cde

It works very well for me so far.