You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Pipenv installs sub dependencies when parent package is installed. If we attempt to remove any of its sub dependencies, they are actually removed from the environment but not from lock file. The expected behaviour is that pipenv locking should fail as the parent package cannot work without its dependencies.
Expected result
Pipenv Lock should fail
Actual result
Pipenv Lock was passed and sub-package was removed from environment, but not from the lock. Now lock file and environment are inconsistant.
Steps to replicate
>pipenv install mongoengine
Installing mongoengine...
Resolving mongoengine...
Added mongoengine to Pipfile's [packages] ...
✔ Installation Succeeded
Pipfile.lock not found, creating...
Locking [packages] dependencies...
Building requirements...
Resolving dependencies...
✔ Success!
Locking [dev-packages] dependencies...
Updated Pipfile.lock (1942dae93a8d933410c6f56c0db13b0782e52730353e84787fde525dcd3f4a17)!
Installing dependencies from Pipfile.lock (3f4a17)...
Mongoengine depends on pymongo, which is actually being installed into environment
Issue description
Pipenv installs sub dependencies when parent package is installed. If we attempt to remove any of its sub dependencies, they are actually removed from the environment but not from lock file. The expected behaviour is that pipenv locking should fail as the parent package cannot work without its dependencies.
Expected result
Pipenv Lock should fail
Actual result
Pipenv Lock was passed and sub-package was removed from environment, but not from the lock. Now lock file and environment are inconsistant.
Steps to replicate
Mongoengine depends on pymongo, which is actually being installed into environment
Attempt to uninstall pymongo
Verifying pymongo in environment
But pymongo is present in the lock file. Expecting pymongo to be present in lockfile as well as in environment!
Pipenv version:
'2023.11.15'
OS Name:
'posix'
User pip version:
'23.3.1'
Contents of
Pipfile
:Contents of
Pipfile.lock
:The text was updated successfully, but these errors were encountered: