Unverified50% confidenceSolutionExact time
In a library project, if uv.lock pins old dependency versions from before Python 3.15 support, deleting uv.lock causes uv to re-resolve dependencies and choose new versions that support Python 3.15, thereby resolving the build error.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
11/2/2026
First Seen
Valid until: 1/31/2027
Sources
Related Entities
Related Claims
UnverifiedBy convention, Python library projects should not include a uv.lock file, because pinning versions affects downstream projects; therefore a library project's uv.lock is usually written into .gitignore.76% similarUnverifiedv1.8.0 fixed a crash in Python 3.13 environments triggered when a stream was still open at program exit.71% similarVerifiedPython's Global Interpreter Lock (GIL) limits true multi-threaded parallelism; Python 3.13 has begun advancing experimental GIL-free support (PEP 703).69% similarUnverified安装 Python 源码时必须使用 altinstall 而非 install,altinstall 只创建带版本号的命令(如 python3.14),不会覆盖系统的 python3 软链接66% similarUnverifieduv.lock is a lock file generated by the Python package manager uv that precisely records the specific versions of all dependency packages in the current environment.66% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1124866API
curl https://kongchang.com/api/v1/knowledge/claims/1124866MCP
get_claim(id=1124866)