So I haven't used mach-nix, but from what I see it provides its own way of specifying dependencies. While in case of poetry2nix you are using poetry for depende

So I haven't used mach-nix, but from what I see it provides its own way of specifying dependencies. While in case of poetry2nix you are using poetry for dependency management and poetry2nix just translates it to Nix. The biggest benefit for using poetry is the dependency resolver which is much smarter than in pip and actually finds packages that match the version requirements (although looks like mach-nix also has a smart resolver. Other benefits are: * nice CLI * ability to package application and upload to PyPI * poetry can still be used by people who don't use Nix Regarding non-python dependencies, this is solved by overrides file[1]. That way most of the time you don't have to think about it. You can also override the override in your project as well. [1] https://github.com/nix-community/poetry2nix/blob/master/overrides.nix https://github.com/nix-community/poetry2nix/blob/master/over...