> venv: Builtin but it is dependent on its host Python. You recreate venvs, you can't copy them.
If you're re-creating a container for the same platform etc. I can't see why it wouldn't work. Aside from third-party packages that include non-Python code, the only thing that really breaks is the paths. (Unfortunately those are all over the place with traditional venv setups, but I'm confident that all of them can be made relative with a bit of setup work plus cooperation from installer tools. Planning to demonstrate it with my own tools, in fact.)
> python-build-standalone requires a musl system installation.
Requires for what, exactly? I'm on a glibc Linux and uv has no problem using the python-build-standalone builds to provide me with Python (I already build it myself, but I thought I'd test it out for PyPy....)
zahlman•2mo ago
If you're re-creating a container for the same platform etc. I can't see why it wouldn't work. Aside from third-party packages that include non-Python code, the only thing that really breaks is the paths. (Unfortunately those are all over the place with traditional venv setups, but I'm confident that all of them can be made relative with a bit of setup work plus cooperation from installer tools. Planning to demonstrate it with my own tools, in fact.)
> python-build-standalone requires a musl system installation.
Requires for what, exactly? I'm on a glibc Linux and uv has no problem using the python-build-standalone builds to provide me with Python (I already build it myself, but I thought I'd test it out for PyPy....)