Python
/
uv
mirror of https://github.com/astral-sh/uv
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
uv/crates/uv-virtualenv
History
Charlie Marsh 2fad82c735
Set base executable when returning virtual environment (#11209) 
## Summary

I'm not sure that this has much of an effect in practice, but currently,
when we return a virtual environment, the `sys_base_executable ` of the
parent ends up being retained as `sys_base_executable` of the created
environment. But these can be, like, subtly different? If you have a
symlink to a Python, then for the symlink, `sys_base_executable` will be
equal to `sys_executable`. But when you create a virtual environment for
that interpreter, we'll set `home` to the resolved symlink, and so
`sys_base_executable` will be the resolved symlink too, in general.
Anyway, this means that we should now have a consistent value between
(1) returning `Virtualenv` from the creation routine and (2) querying
the created interpreter.
 		2025-02-04 22:32:47 +00:00
..
src Set base executable when returning virtual environment (#11209) 2025-02-04 22:32:47 +00:00
Cargo.toml Use base Python for cached environments (#11208) 2025-02-04 17:23:06 -05:00
README.md Rename `gourgeist` to `uv-virtualenv` (#2118) 2024-03-01 14:02:40 -05:00

README.md

uv-virtualenv

uv-virtualenv is a rust library to create Python virtual environments. It also has a CLI.