Skip to content Skip to sidebar Skip to footer

How Does Pip Determine The Version Of A Dependency Of Multiple Dependents

Let's assume we have the following dependency tree in Python using PIP as package installer: A==1.2.1: | - B==1.5.4 | - C==?.?.? D==1.3.0: | - C==?.?.? Let's also assume that

Solution 1:

When pip installs a package, it automatically installs any dependent Python packages without checking if these conflict with previously installed packages. It will install a package and any of its dependencies regardless of the state of the existing installation. Because of this, a user with a working installation of, for example, Google Tensorflow, can find that it stops working having used pip to install a different package that requires a different version of the dependent NumPy library than the one used by Tensorflow. In some cases, the package may appear to work but produce different results in detail.

Anaconda (Python distribution) - Wikipedia

Solution 2:

On this topic, things will change relatively soon. Since pip's developers are currently working on a new dependency resolver:


To test it today, you might want to install pip 20.2b1 and enable the unstable feature "resolver", with for example either one of the following:

  • PIP_UNSTABLE_FEATURE=resolver python -m pip install SomeProject
  • python -m pip --unstable-feature=resolver install SomeProject

See the following link for more details:


Other references:


Updatepip 20.2

Post a Comment for "How Does Pip Determine The Version Of A Dependency Of Multiple Dependents"