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
..
policies	Add policies reference section and license document (#9367)	2024-12-03 10:56:32 -06:00
troubleshooting	Add best-practice flags to pip install example in troubleshooting guide (#11194)	2025-02-03 20:13:55 +00:00
benchmarks.md	Add link to benchmarks in documentation (#6257)	2024-08-20 12:54:46 -04:00
cli.md	Add support for respecting VIRTUAL_ENV in project commands via --active (#11189)	2025-02-05 10:12:19 -06:00
index.md	Add policies reference section and license document (#9367)	2024-12-03 10:56:32 -06:00
resolver-internals.md	Update resolver internals docs (#11098)	2025-02-04 13:06:27 +00:00
settings.md	Fix typo in no-deps docs/comments/cli description (#11073)	2025-01-29 11:55:40 -06:00