Skip to content

Feat: Create a cached lock file for uv run with scripts #9688

@notatallshaw

Description

@notatallshaw

This is a follow up to #7538, I wanted to make a clear feature request. Basically I don't want uv run ... to resolve when it's already done it once, unless I pass something like uv run --upgrade ....

The current behavior is problematic when the network is having transient issues or is very slow, for example a firewall decides to start blocking access to a package then uv run fails even though it previously installed all the dependencies, or if the network is very slow and is randomly dropping packets then every time you run uv run you end up with it saying ⠷ Resolving dependencies... for several seconds.

In general, I think the expected user experience (perhaps incorrectly) of uv run ... is there is no network activity required unless absolutely necessary.

FYI, I'm not currently impacted by this issue, so it's not a big priority for me, but I have seen it in the past, and in general it does feel like a better user experience.

Metadata

Metadata

Assignees

Labels

needs-decisionUndecided if this should be done

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions