uv/crates/uv-workspace at zb/docs-bench-align - mirrors/uv

mirrors/uv

mirror of https://github.com/astral-sh/uv.git synced 2025-08-04 02:48:17 +00:00

History

Zanie Blue 989b103171 Add support for respecting `VIRTUAL_ENV` in project commands via `--active` (#11189 ) I think `UV_PROJECT_ENVIRONMENT` is too complicated for use-cases where the user wants to sync to the active environment. I don't see a compelling reason not to make opt-in easier. I see a lot of questions about how to deal with this warning in the issue tracker, but it seems painful to collect them here for posterity. A notable behavior here — we'll treat this as equivalent to `UV_PROJECT_ENVIRONMENT` so... if you point us to a valid virtual environment that needs to be recreated for some reason (e.g., new Python version request), we'll happily delete it and start over.	2025-02-05 10:12:19 -06:00
..
src	Add support for respecting `VIRTUAL_ENV` in project commands via `--active` (#11189 )	2025-02-05 10:12:19 -06:00
Cargo.toml	Enable `--all-packages --frozen` in `uv sync` and `uv export` (#8760 )	2024-11-02 02:48:55 +00:00

Add support for respecting VIRTUAL_ENV in project commands via --active (#11189 )

I think `UV_PROJECT_ENVIRONMENT` is too complicated for use-cases where
the user wants to sync to the active environment. I don't see a
compelling reason not to make opt-in easier. I see a lot of questions
about how to deal with this warning in the issue tracker, but it seems
painful to collect them here for posterity.

A notable behavior here — we'll treat this as equivalent to
`UV_PROJECT_ENVIRONMENT` so... if you point us to a valid virtual
environment that needs to be recreated for some reason (e.g., new Python
version request), we'll happily delete it and start over.

2025-02-05 10:12:19 -06:00

src Add support for respecting VIRTUAL_ENV in project commands via --active (#11189 ) 2025-02-05 10:12:19 -06:00

Cargo.toml Enable --all-packages --frozen in uv sync and uv export (#8760 ) 2024-11-02 02:48:55 +00:00