Improve UX when `uv add` or `uv sync` are run in a directory with no `pyproject.toml` · astral-sh/uv#12988

(1 comment) (1 reaction) (0 assignees)Rust (84,934 stars) (3,111 forks)batch import

enhancementerror messageshelp wanted

Description

Summary

Currently if uv add or uv sync are run in a directory with no pyproject.toml, the resultant error message is:

$ mkdir testcase-uv && cd $_
$ uv add urllib3
error: No `pyproject.toml` found in current directory or any parent directory
$ uv sync
error: No `pyproject.toml` found in current directory or any parent directory

To improve the UX for users migrating from pip (or uv's uv pip interface), it would help if this error message hinted that the user should probably run uv init or else see the uv getting started docs.

Example

Perhaps something roughly like this?

$ uv add urllib3
error: No `pyproject.toml` found in current directory or any parent directory.
To create one run `uv init`, or see: https://docs.astral.sh/uv/guides/projects/

Contributor guide

Tech stack: rustpython
Domain: clideveloper experience
Issue type: feature
Difficulty: 2
Estimated time: under 1 hour
Activity status: fresh
Clarity: clear
Prerequisites: Rust programming basicsFamiliarity with uv CLI codebase
Newbie friendliness: 85
Research direction: Find where the error message 'No `pyproject.toml` found in current directory or any parent directory' is raised, likely in a CLI handler for `uv add` and `uv sync`. Modify the error message to include a hint about running `uv init` and a link to the docs. Check existing pattern for similar error hints in the codebase.