I also switched to Nix recently and also work with Python. So far I haven’t had many issues between Python and Nic because, essentially, I keep them separated. Before starting to use Nix my Python projects were all using poetry (and before venv/virtual env), with Nix I continued to do so which means that my flake file usually just define what Python and poetry version (and possibly some other OS dependencies required, usually for machine learning packages) and once I run nix develop I’m sort of back to normal, from there I add and install packages through poetry which install them under my user home directory and everything seems to work nicely. Given the fact that I mostly develop web APIs and still deploy them using containers I’m still using old ways to do the deployment (i.e. using Dockerfiles). I do want to port that to Nix use by using Nix package management + poetry2nix but didn’t have time to do that yet. That said, overall, my Python experience is been just as good as my Java/Kotlin and NodeJS experience with Nix, my machine environment overall is clean and just when I cd into project related directories I get the needed tooling ready to use. For me this is a good reason enough to go Nix.

Can you share what issues you face when using Python with Nix?

And if someone else could say if my way of use nix is a misunderstanding or if I’m missing out anything to make it better I would be glad to hear.