Delete the uv.lock File to Resolve Python 3.15 Dependency Errors

Since upgrading to Python 3.15, some developers have reported intermittent dependency errors that trace back to the uv.lock file. The lock file can capture a specific version of a package that hasn't yet released a wheel compatible with the newest interpreter.

Most library projects deliberately omit a uv.lock file, as locking versions for downstream users is considered impolite. However, running commands like uv run pytest often generates a temporary uv.lock, which is typically ignored via .gitignore and never committed.

When that temporary lock pins a package lacking a Python 3.15 wheel, the build fails. An example surfaced earlier today with watchfiles==1.1.1, where the build process halted with a maturin error because the interpreter version was too new.

The practical rule emerging from these incidents is straightforward: if in doubt, delete the uv.lock file. Removing the lock forces uv to resolve dependencies against the latest available releases, bypassing the stale pin.

While this approach clears the immediate error, developers should remain aware that permanent lock files are valuable for reproducible environments. Use them judiciously, and consider regenerating a fresh lock after confirming compatibility with Python 3.15.