[PROTON-2217] Python detection logic prefers python2 over python3 when both are installed

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: proton-c-0.31.0
• Fix Version/s: proton-c-0.34.0
• Component/s: build, proton-c, python-binding
• Assignee: Jiri Daněk
• Reporter: Jiri Daněk
• Created: 12/May/20 12:59
• Updated: 12/Apr/21 08:35
• Resolved: 21/Feb/21 10:08

Description

I have the same experience that was reported elsewhere:

For me, the find_package(PythonInterp) call was always finding the older interpreter (2.7) even though everything pointed to the newer one (3.6). (from https://reviews.llvm.org/D64881)

This behavior is unfortunate on Ubuntu 20.04 Focal, where both python2 and python3 are available, but pip for python2 is not packaged. Therefore it makes sense to build proton with python3; which would make sense anyways, since Python 2.7 is deprecated by the Python Software Foundation nowadays..

Besides removing python2 as discussed on the linked page, there is currently nicer way to force python3 that worked for me, by setting -DPYTHON_EXECUTABLE=/usr/bin/python3 CMake variable.

Related dispatch issue, DISPATCH-187

Issue Links

• is related to: DISPATCH-1942 Use modern idiomatic cmake 3.x
• relates to: PROTON-2219 Upgrade .travis.yml to test on a good cross-section of available Ubuntu versions