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
..
projects	Add support for respecting VIRTUAL_ENV in project commands via --active (#11189)	2025-02-05 10:12:19 -06:00
cache.md	Allow environment variables to be included in cache keys (#10170)	2024-12-26 15:31:49 +00:00
index.md	Reorganize the project concept documentation (#9121)	2024-11-19 13:52:12 -06:00
python-versions.md	Touch-ups to the Python install guide (#11116)	2025-01-30 13:56:53 -06:00
resolution.md	Add Requires-Python upper bound behavior to the docs (#10964)	2025-01-28 12:17:34 -05:00
tools.md	docs(tools.md): remove hyphenation for consistency (#10321)	2025-01-06 09:33:46 -05:00