Unused packages aren’t typically a problem unless you imperatively change your systems state. Otherwise, If you remove it from your configuration.nix, it’s removed when you switch to your next build. Previous builds/generations keep those versions of those packages, which wastes space, but you can specify garbage collection to remove generations older than a month
My only complaint so far is the best way to properly make a development shell for a python project is either with a still somewhat experimental feature called flakes, or a 3rd party solution poetry2nix. Im probably going to switch to using docker/podman for python projects.
On the other hand, pip is the worst package manager, so being incentivized away from it is kind of a plus
Exactly, like ansible.
Unused packages aren’t typically a problem unless you imperatively change your systems state. Otherwise, If you remove it from your configuration.nix, it’s removed when you switch to your next build. Previous builds/generations keep those versions of those packages, which wastes space, but you can specify garbage collection to remove generations older than a month
My only complaint so far is the best way to properly make a development shell for a python project is either with a still somewhat experimental feature called flakes, or a 3rd party solution poetry2nix. Im probably going to switch to using docker/podman for python projects.
On the other hand, pip is the worst package manager, so being incentivized away from it is kind of a plus