Skip to content

uv cache size #15821

@charlesnicholson

Description

@charlesnicholson

Summary

Since uv's cache growth is unbounded, it would be helpful to have a built-in subcommand uv cache size or similar that can be parsed by scripts to decide whether or not to blow away the cache. Since uv cache prune already reports the cache size, maybe that logic would be easy to extract and offer up as a new subcommand?

Example

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or improvement to existing functionality

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions