venv: --copies?

[gkze]

Got it to compile on Nix (was a pain because of openssl-sys :) ). Now the problem is the venv being constructed with symlinks instead of copies. Would it make sense to have a --copies/--symlinks a la venv? Or symlink the core installation and write installed packages to the venv instead of the system directory?

[Vigilans]

I am mounting my home directory to devcontainer to reuse my user configs, and I have a venv dedicated for my user. Without --copies to create a self contained venv, the user-wide venv may not find the python through the symlink, or symlinked to different version in the devcontainer.

[konstin]

We're now supporting uv venv --link-mode copy, which will copy the installed packages, even though we're still symlinking the python interpreter.

[zanieb]

Is this still an issue because we're not copying the interpreter? Should we respect --link-mode for the interpreter too?