> It maintains a global dependency chain across your entire machine. There are per python binary, per user, per virtualenv installation (per project or per wha

> It maintains a global dependency chain across your entire machine. There are per python binary, per user, per virtualenv installation (per project or per whatever you like) that make the conflict less likely. Sometime packages "vendor" their dependencies e.g., there is `pip._vendor.requests` (thus you may have different `requests` versions in the same environment). There were setuptools' multi-version installs https://packaging.python.org/guides/multi-version-installs/ https://packaging.python.org/guides/multi-version-installs/ (I don't remember using it explicitly ever -- no need)