-
Notifications
You must be signed in to change notification settings - Fork 19
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
Implement a lockfile format #31
Comments
This has been picked up by volunteers, who've worked on this since Feb 2021 -- PEP 665 and https://discuss.python.org/t/11736/ is the current effort. |
I think the "and implement" part still might require funding here? |
Ok, I'll re-open and update the title. |
What is left to do here ? @xmunoz @pradyunsg PEP 665 has been rejected, is there any new follow-up PEP ? |
A follow up PEP, specifying a lock file format that also caters to source distributions (since that has been requested).
Not at this time, no.
Not at this time, no.
Not at this time, no. |
pip
currently usesrequirements.txt
to specify dependencies; it can specify versions of packages but not hashes. The newer pipfile format can include hashes, which some users prefer. Butpip
doesn't yet supportpipfile
, so many users are blocked from using hashes to better secure their Python runtimes. We have made some progress toward standardizing an interoperable lockfile format, but we need to finish that design standardization and consensus-gathering work and implement it inpip
,pipenv
, and related tools. We'd need Python engineering work and project management to develop and deploy this.Related: PEP 650 -- Specifying Installer Requirements for Python Projects
The text was updated successfully, but these errors were encountered: