-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Description
We are currently relying on project.pipfile_location
in order to determine lockfile_location
. There are a few reasons for this, one of which is that we actually need a pipfile to exist in most cases in order to perform a comparison of the known pipfile hash which is stored in the lockfile and likely would require --ignore-pipfile
to make this all work properly.
-
We still probably need to raise an exception if this option isn't provided because everything else will be broken the minute you perform any other update operations. You can however install from the lockfile alone
-
Alternatively, we can shim all of the pipfile references to be ok with the existence of a lockfile instead
-
See also: pipenv sync fails without Pipfile present #2834 & pipenv sync unexpected behavior when Pipfile missing #1977