Sure, but in the case where you upgrade python and it affects python packages it would affect global packages and a venv in the same way.
upgrading your base image won’t affect your python packages
Surely if upgrading python will affect your global python packages it will also affect your venv python packages?
you can use multi stage builds to create drastically smaller final images
This can also be done without using venv's, you just need to copy them to the location where global packages are installed.
I don't think they have anything to do with each other, it looks like prefix.dev uses conda packages.
Yeah it is, eventually they want UV to have feature parity with rye and rye will basically just be a pointer to UV
Early on uv was only trying to replace pip. This latest update is a big step towards becoming a poetry (and pyenv/pipx) replacement too.
It worked for me with just: virtualisation.libvirtd.enable = true;
in the configuration.nix
.
Stable channels provide conservative updates for fixing bugs and security vulnerabilities, but do not receive major updates after initial release.
If you want up to date packages then use the unstable channel.
Nix has the most unique packages and the most up to date packages of any Linux software repository. It has substantially more fresh packages than Arch or Alpine (which you say does a better job in a separate comment).
Source:https://repology.org/repositories/graphs
Yeah I agree, I am sure they are missing some obscure stuff. But in practise it has everything that I use and there has been no need for me to touch flatpak/appimage/snap
yep, I mean a GUI based software centre
NixOS:
- Largest and most up to date package repository (no need for flatpack/appimage/snap ect)
- Reproducible
- Declarative
- Rollbacks you can select at boot time
- No dependency conflicts
I think it will easily be the number 1 distro if/when they can :
- the steep learning curve (e.g. have a gui installer EDIT: As in a GUI software centre)
- documentation
- have more tools use nixos and have nixos in mind (e.g. there are a couple of tools that didn't work for me because of specific C libraries not beeing present/configured on nixos that are present on other distros. some libraries implicitly expect these to be present).
If you do multi stage builds (example here) it is slightly easier to use venvs.
If you use the global environment you need to hardcode the path to global packages. This path can change when base images are upgraded.