I did not really want to go too deep into that discussion, but it might have been a mistake on my side not to provide more context.
If you want to use the standard Python workflow (with pip, poetry and the such), you’ll use a virtual env in your project and install the python dependencies with those tools.
Most of the time, they’ll download the wheel. The issue is that those wheels provide binaries executables and binaries that depend on dynamic linking, and on NixOS it does not work well.
Any lib without binaries is fine, but anything like numpy, pandas, or pytorch will most likely crash when you try to use them.
VSCode, Pycharm and many tools rely on such a venv. You could say “just enter a nix shell” but a lot of tooling wont support that (hello VSCode). And I can’t wait for a patch that might never come: I need to get stuff done today at my job.
So I just patch the binaries rpath and interpreter.
There is also the fact that I think most of the time it is not a good idea to use Nix to manage the Python dependencies of your local environment, but I need more time to open a discussion about it, and would prefer not to pollute the conversation here with a debate. Please help me in that regard