-
Notifications
You must be signed in to change notification settings - Fork 760
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add uv init --virtual
#5396
Add uv init --virtual
#5396
Conversation
crates/uv-workspace/src/workspace.rs
Outdated
"Nested workspaces are not supported, but outer workspace includes existing workspace: `{}`", | ||
pyproject_toml_path.user_display().cyan(), | ||
outer_workspace_root.simplified_display().cyan(), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Running from the current directory, this message is "Nested workspaces are not supported, but outer workspace includes existing workspace: ``", seems not clear.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good call.
fn init_virtual_workspace(path: &Path, isolated: bool) -> Result<()> { | ||
// Check nested workspaces. | ||
if !isolated { | ||
check_nested_workspaces(path, &DiscoveryOptions::default()); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we warn or abort if nested workspace detected?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think warn is ok.
Summary
Add
uv init --virtual
to create an explicit virtual workspace.Relates to #5338