We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
❯ lsd --tree .venv/ .venv └── magic.txt ~/git/github/tox-uv on main [!?⇕] ❯ uv venv Using Python 3.12.1 interpreter at: /Users/bgabor8/.pyenv/versions/3.12.1/bin/python3 Creating virtualenv at: .venv uv::venv::creation × Failed to create virtualenv ╰─▶ The directory `.venv` exists, but it's not a virtualenv
tox likes to put a few other files (tmp folder, .tox-info.json, etc) in this folder that breaks uv venv....
tox
tmp
.tox-info.json
uv venv
Is fine if is hidden behind a --allow-extra-content flag.
--allow-extra-content
The text was updated successfully, but these errors were encountered:
I wonder if this should just be gated by a simple --force flag.
--force
Sorry, something went wrong.
Works for me 😀
Allow --force to overwrite existing virtualenv (#2548)
614c073
## Summary Closes #2529. ## Test Plan - `mkdir .venv` - `touch .venv/foo` - `cargo run venv` (ensure failure) - `cargo run venv --force` (ensure success) - `cargo run venv --force` (ensure success again)
charliermarsh
Successfully merging a pull request may close this issue.
tox
likes to put a few other files (tmp
folder,.tox-info.json
, etc) in this folder that breaksuv venv
....Is fine if is hidden behind a
--allow-extra-content
flag.The text was updated successfully, but these errors were encountered: