Simon Willison Resolves Python Dependency Errors
Simon Willison resolves Python dependency errors by deleting uv.lock file. This solution helps with issues after switching to Python 3.15.
Original reporting · simonwillison.net
Original: “If in doubt, delete the uv.lock file”
Read “If in doubt, delete the uv.lock file” at Simon Willison →How this was written. GDS wrote this article with a language model from Simon Willison’s reporting (model: @cf/meta/llama-3.3-70b-instruct-fp8-fast); it describes that reporting rather than adding to it. The original, linked above, is the full story.
Key points from Simon Willison’s report
- Simon Willison experiences Python dependency errors after switching to Python 3.15.
- Deleting the uv.lock file resolves the dependency errors.
- Most of Simon Willison's projects are libraries without a uv.lock file.
Simon Willison reported that he has been experiencing occasional confusing Python dependency errors since switching to Python 3.15. The errors have prompted him to remember a specific rule to resolve the issues.
According to Simon Willison, the rule is to delete the uv.lock file when in doubt. This approach has been helpful in addressing the dependency errors that have arisen since the switch to Python 3.15.
Most of Simon Willison's projects are libraries, which typically do not include a uv.lock file. However, when a uv.lock file is present, deleting it can help resolve Python dependency errors, as noted by Simon Willison.
Questions and answers
What resolves Python dependency errors?
Deleting the uv.lock file resolves the errors.
What prompted Simon Willison to find a solution?
Switching to Python 3.15 prompted Simon Willison to find a solution to the dependency errors.
