Yea this can be very annoying when a package is not already in nixpkgs or it's out of date. There was a similar issue if you didn't use Python virtualenvs prop

Yea this can be very annoying when a package is not already in nixpkgs or it's out of date. There was a similar issue if you didn't use Python virtualenvs properly, which was an early source of frustration for me personally.