[clug] Tracking Down the Reason For a Pip Install

jm jeffm at ghostgun.com
Tue Jan 24 03:56:46 UTC 2017

On some of the systems I run pip and rpm are having a disagreement about
the version of a package installed. It gets installed by yum first then
something else gets installed via pip and finds this package to be too
old so installs a later version via pip. Every python program is suppose
to be running in its own virtualenv so this shouldn't occur. Is there
anyway to track down what is triggering this disagreement between
package managers?


More information about the linux mailing list