uv/docs/concepts/projects
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
..
build.md Explain build frontend vs. build backend (#11094) 2025-01-30 19:48:47 +00:00
config.md Add support for respecting VIRTUAL_ENV in project commands via --active (#11189) 2025-02-05 10:12:19 -06:00
dependencies.md Add documentation for uv add -r (#10926) 2025-01-23 21:34:50 -06:00
index.md Reorganize the project concept documentation (#9121) 2024-11-19 13:52:12 -06:00
init.md Fix ruff linting warnings from generated template files for extension modules (#10371) 2025-01-07 17:07:44 +00:00
layout.md Improve content on project configuration (#9235) 2024-11-20 08:49:51 -06:00
run.md Add docs for signal handling (#11041) 2025-01-29 08:27:52 -06:00
sync.md Add Git SHA locking behavior to docs (#11125) 2025-01-31 12:11:04 -06:00
workspaces.md docs(workspaces): remove build-system (#10636) 2025-01-15 11:46:35 -06:00