Pep 751: Pylock.toml
Posted4 months agoActive4 months ago
peps.python.orgTechstory
skepticalmixed
Debate
60/100
PythonPackage ManagementStandardization
Key topics
Python
Package Management
Standardization
Discussion around PEP 751 proposing a new lock file format for Python, Pylock.toml, and its potential adoption.
Snapshot generated from the HN discussion
Discussion Activity
Light discussionFirst comment
2h
Peak period
2
1-2h
Avg / period
1.3
Key moments
- 01Story posted
Sep 11, 2025 at 6:54 PM EDT
4 months ago
Step 01 - 02First comment
Sep 11, 2025 at 8:26 PM EDT
2h after posting
Step 02 - 03Peak activity
2 comments in 1-2h
Hottest window of the conversation
Step 03 - 04Latest activity
Sep 12, 2025 at 6:45 AM EDT
4 months ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
ID: 45216926Type: storyLast synced: 11/17/2025, 6:14:48 PM
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.
That said, I do think having reproducible builds as an explicit goal is important here, as several pre-existing formats like requirements.txt are too lax on that front.
[0]: https://discuss.python.org/t/community-adoption-of-pylock-to...
A new format can fix issues that exist in the existing ones, but does that benefit outweigh the benefit of adopting the most popular existing option and having a free and massive heard start towards getting everyone to adopt it and retire the other four?
But no, there wouldn't have been a coherent metric for "most popular", and anyway the existing designs were independently trying to solve subtly different problems without concern for anyone else. The new format was designed based on getting the relevant parties to talk to each other and figure out what would be necessary for interoperability.