Charlie Marsh eb14056e9c Add support for virtual projects (#6585) ... ## Summary The basic idea here is: any project can either be a package, or not ("virtual"). If a project is virtual, we don't build or install it. A project is virtual if either of the following are true: - `tool.uv.virtual = true` is set. - `[build-system]` is absent. The concept of "virtual projects" only applies to workspace member right now; it doesn't apply to `path` dependencies which are treated like arbitrary Python source trees. TODOs that should be resolved prior to merging: - [ ] Documentation - [ ] How do we reconcile this with "virtual workspace roots" which are a little different -- they omit `[project]` entirely and don't even have a name? - [x] `uv init --virtual` should create a virtual project rather than a virtual workspace. - [x] Running `uv sync` in a virtual project after `uv init --virtual` shows `Audited 0 packages in 0.01ms`, which is awkward. (See: https://github.com/astral-sh/uv/pull/6588.) Closes https://github.com/astral-sh/uv/issues/6511.		2024-08-27 13:42:46 -04:00
..
src	Add support for virtual projects (#6585)	2024-08-27 13:42:46 -04:00
Cargo.toml	Make more informative warning message when failed to parse pyproject.toml (#6009)	2024-08-11 21:13:14 +00:00