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'm not really against it if there is a demand and people want to buy/sell/trade here. If buy/sell/trade gets too much we could restrict it to a sticky thread.
It might be easier for people to find buyers/sellers on the framework forum category that @[email protected] pointed out though.
He is a front end dev/engineer and he mainly talks about the UI (which is his expertise).
Here are their repos: https://github.com/zen-browser
and here is a video from Theo on youtube looking into zen browser: https://www.youtube.com/watch?v=tKM2N4TQHQY
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
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.