Show a better error when a uv lockfile is used in `-r` · astral-sh/uv#16192

(3 评论) (3 反应) (0 负责人)Rust (84,934 star) (3,111 fork)batch import

error messageshelp wanted

描述

e.g., if you try to use uv lock --script action.py then -r action.py.lock

error: Couldn't parse requirement in `action.py.lock` at position 0
  Caused by: no such comparison operator "=", must be one of ~= == != <= >= < > ===
version = 1
        ^^^

We can do better by detecting our own lockfile format

贡献者指南

技术栈: rust
领域: clideveloper experience
议题类型: feature
难度: 3
预计时间: half day
活动状态: fresh
清晰度: clear
前置要求: Basic RustUnderstanding of uv lockfile format
新手友好度: 70
研究方向: The issue is about improving error handling when a user mistakenly passes a uv lockfile to the ` r` flag. Start by examining how ` r` arguments are parsed in the CLI, likely in the `uv` crate's argument handling or in the lockfile parser. Look for where the error message 'Couldn't parse requirement' is generated and trace back to understand how file types are detected. The goal is to detect if the file is a uv lockfile by checking its contents (e.g., the presence of 'version = 1' header) and emit a clearer, user friendly error message.