-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Allow uv run
to be used without --no-project
#13599
base: main
Are you sure you want to change the base?
Conversation
Oh, no shebang update until astral-sh/ruff#13021, I'll revert those. |
|
I still don't like this. If someone wants to contribute a small fix to typeshed, e.g. stubs for a simple library, they shouldn't be thrown on a tangent about a tool named
I think it is safe to assume that anyone contributing to typeshed already knows how to run Python on their own system. Figuring out whether to put |
Yeah my comment at #13597 (comment) will apply here as well
I'll update this PR
|
uv run
(no more python vs python3)uv run
to be used without --no-project
This PR is now only scoped to allowing using You may have reasons to not want to modify the |
Co-authored-by: Akuli <[email protected]>
This enables running
uv run
without having to add--no-project
every time. Until astral-sh/uv#8666, this requires adding a[project]
section topyproject.toml
and.gitignoring
theuv.lock
file.Using
uv run
is optional. "medium to advanced" python users already know to activate their venv and use the right py/python/python3 command if they want to.Contributors who want to use
uv run
but with a custom venv can do so withuv run --active
. I use that on WSL with a.venv-linux
venv.