Unverified50% confidenceFactExact time
By 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.
1
Sources
50%
Confidence
Long-term
Relevance
11/2/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedIn 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.76% 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.69% similarVerifiedDue to the existence of the GIL (Global Interpreter Lock), Python only allows one thread to execute Python bytecode at any given moment, creating a bottleneck in CPU-intensive concurrent scenarios67% similarUnverifiedPixi的锁文件覆盖范围延伸到系统级二进制依赖,这是pip/uv等纯Python工具无法实现的67% similarUnverifiedlockfile 是包管理器生成的依赖版本快照文件,常见形式包括 npm 的 package-lock.json、pnpm 的 pnpm-lock.yaml 以及 yarn 的 yarn.lock66% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1124857API
curl https://kongchang.com/api/v1/knowledge/claims/1124857MCP
get_claim(id=1124857)