-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CEP: Standardize Lock File Format #107
Comments
xref #79 |
Also: #81 |
Tangentially related: PEP 751, where a multi-year discussion is now winding down towards a possible conclusion. |
Thanks for linking to that. I will be carefully reading that proposal and learn more about the ongoing discussions. |
Hm, I thought the Python lockfiles were not going to make it in the end? Source: https://bsky.app/profile/snarky.ca/post/3ldp5zvst4c2v |
It got trimmed down because people (still) couldn't agree on much of the semantics. But the discussion has lots of material on this subject. |
To facilitate cross tool compatibility (e.g. conda, mamba, and pixi), we should standardize a lock file format so that all tools are able to read and write the same lock files.
Currently, there are two options:
The latter lock file type has seen more recent development, and made several improvements over what was initially developed by conda-lock; therefore, it would make a better choice to use as the model for standardization.
The CEP to be written shall include a precise description of how the lock file is to be formatted and include a reference link to the current implementation in rattler-lock.
The text was updated successfully, but these errors were encountered: