Skip to content
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

Make Pipfile.lock mandatory when using Pipenv #1702

Open
edmorley opened this issue Nov 25, 2024 · 0 comments
Open

Make Pipfile.lock mandatory when using Pipenv #1702

edmorley opened this issue Nov 25, 2024 · 0 comments
Assignees

Comments

@edmorley
Copy link
Member

edmorley commented Nov 25, 2024

Using Pipenv without a lockfile can result in nondeterministic package installs, and so for some years if Pipfile.lock is missing we've emitted a recommendation in the build log to add it.

In addition, Pipenv has also since deprecated the --skip-lockfile feature upstream.

As such, we'd like to sunset support for using Pipenv without a lockfile.

A deprecation warning has been added in #1695 - once that has been showing for a bit we can then make Pipfile.lock mandatory when using Pipenv.

GUS-W-17308738.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant