-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
venv: --copies? #2103
Comments
I am mounting my home directory to devcontainer to reuse my user configs, and I have a venv dedicated for my user. Without |
We're now supporting |
Is this still an issue because we're not copying the interpreter? Should we respect |
I'm trying to resolve an issue where I'm not sure this is the source of my issue, but I wanted to try a copy with the interpreter included |
I used uv to bootstrap python for an old embedded armv7 platform that had no python3 or package manager. My goal was to create a venv folder that was portable enough such that I could deploy it to this platform multiple times without internet or needing the uv binary installed. I tried forcing it by copying the interpreter into my venv folder but it seemed like some libraries were still linked or missing. I eventually set my
This is the closest I could get to a portable project when bootstrapping with |
This is also in line with my proposal in #11773 |
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 lavenv
? Or symlink the core installation and write installed packages to the venv instead of the system directory?The text was updated successfully, but these errors were encountered: