konsti a89e146107 Initial workspace support (#3705) ... Add workspace support when using `-r <path>/pyproject.toml` or `-e <path>` in the pip interface. It is limited to all-editable static-metadata workspaces, and tests only include a single main workspace, ignoring path dependencies in another workspace. This can be considered the MVP for workspace support: You can create a workspace, you can install from it, but some options and conveniences are still missing. I'll file follow-up tickets (support in lockfiles, support path deps in other workspace, #3625) There is also support in `uv run`, but we need https://github.com/astral-sh/uv/issues/3700 first to properly support using different current projects in the bluejay interface, currently the resolution and therefore the lockfile depends on the current project. I'd do this change first (it's big enough already), then #3700, and then add workspace support properly to bluejay. Fixes #3404		2024-05-28 07:41:53 +00:00
..
packages	Initial workspace support (#3705)	2024-05-28 07:41:53 +00:00
src/albatross	Discover workspaces without using them in resolution (#3585)	2024-05-21 17:17:26 +00:00
check_installed_albatross.py	Discover workspaces without using them in resolution (#3585)	2024-05-21 17:17:26 +00:00
pyproject.toml	Discover workspaces without using them in resolution (#3585)	2024-05-21 17:17:26 +00:00