Pip using python2 even if running build script with python3

[koliyo]

If I start my build script like this

python3 build.py --build outdated

It will still use pip2 to install the conan packages, see packager.py

conan-package-tools/conan/packager.py

Line 406 in 60ed0b2

self.runner('%s pip install %s' % (self.sudo_command, self.conan_pip_package))

Assuming pip == pip2, which it normally is

[lasote]

I assume that it is hard to know which one to execute, I could add a parameter to specify the "pip" command to run. WDYT?

[koliyo]

Yes, a parameter/environment variable would be helpful. Even better would be automatic detection, but that might be a bit tricky if the naming of python/pip binaries are not standardized across platforms.

To detect the running environment you can use sys.version_info, and if that is version 3, then try using pip3, otherwise pip2. Maybe you need something like this to check if the those binares are available. If not, fall back to pip.

[Croydon]

Since we started moving the build tools slowly to Python 3 this might become obsolete.

[jgsogo]

What about...?

import pip

pip.main(['install', 'whatever'])

or pip._internal.main depending on python version.

or running <path/to/python> -m pip ... where <path/to/python> = sys.executable.

[theodelrieu]

I'd like to get this feature as well 😄