Except python builders in nixpkgs are really brain damaged because of the writers ways they inject search path which for example breaks if you try to execute a separate python interpreter assuming same library environment...

Within the holy church of Nix the sect of Python is troubled one, it can however be tamed into use via vast tomes of scripture. Sadly these times can only be written by those you have truly given their mind and body over to the almighty Nix.

It's not as bad as Common Lisp support which stinks to high heavens of someone not learning the lessons of the Common-Lisp-Controller fiasco

Lisp is of the old gods, only the most brave of Nix brethren dare tread upon their parenthesised ways.

>May I introduce you to our lord and saviour, Nix and it's most holy child nixpkgs!

In this case, instead of working with Python, you change how you manage everything!

The Nix of Python, conda, was already mentioned.

> add about as many quality problems as they fix

I used to have 1 problem, then I used Nix to fix it, now I have 'Error: infinite recursion' problems.

Nix is really the best experience I've had with Python package management but only if all the dependencies are already in nixpkgs. If you want to quickly try something off github it's usually a pain in the ass.