Verified, then logged.
Sun 22 Nov 2026 · 00:33 KST / 15:33 UTC한국어 | ENSearch /

Breaking02 / IT

Python 3.15 dependency errors bring advice to delete uv.lock

uv's documentation tells projects to keep the lock file in version control, while the advice to delete it comes from personal experience.

A developer's hand pauses above a blank-keycap keyboard while an out-of-focus terminal window on the monitor ends in a band of red build-error lines. AI-generated image

Simon Willison deletes the uv.lock file when dependency errors appear after a switch to Python 3.15, according to a blog post published on 1 Nov 2026. The advice applies to users of uv, a Python package and project manager, who move projects with an existing lock file to the new Python release.

An error log in the post records a build failure. The failure is in the Python package watchfiles 1.1.1. According to the post, deleting the file and running uv run pytest again usually resolves the problem.

Compatibility. uv's documentation says uv sync and uv lock prefer previously locked versions when a uv.lock file exists. The PyPI description of watchfiles 1.1.1 gives a supported range of Python 3.9 to 3.14. Python 3.15 falls outside that range.

The uv documentation says of the lock file, "This file should be checked into version control". It gives reproducible installations as the reason. The uv lock --upgrade command is available for updating packages.

Most of Willison's projects are libraries and do not include a uv.lock file, the post explains. Willison considers it rude for a library to lock versions for other projects that use it. Commands such as uv run pytest still tend to leave the file behind.

Licence and platforms. The uv repository lists Apache License 2.0 and MIT, and users choose either licence. Its supported operating systems are macOS, Linux and Windows.

The advice to delete the file comes from Willison's own experience. The post does not give the uv version in use or the share of cases that deletion resolved.