Comment # 1 on bug 1084281 from Simon Lees

(In reply to Christophe Giboudeaux from comment #0)
> feature-suse-python-interp-search-order.patch causes an issue on the KDE CI
> hosts.
> 
> The python2 backend in Cantor no longer builds as shown here:
> https://build.kde.org/job/Applications%20cantor%20kf5-qt5%20SUSEQt5.9/29/
> consoleFull
> 
> The relevant part is here:
> 06:03:01 -- Found PythonLibs: /usr/lib64/libpython3.6m.so (found suitable
> version "3.6.4", minimum required is "2.7") 
> 
> Cantor explicitly tries to find python 2 but due to the patch, CMake ignores
> the version.
> 
> Reverting the patch locally fixes the issue.

Can you give me a link to your CMakeLists.txt, all this patch does is removes
the assumption that  /usr/bin/python is the default python interpreter and
instead looks for a python version that meets the constraints from newest to
oldest. The reason behind this is in openSUSE, python3 is the default but we
have decided not to change /usr/bin/python to python3 for reasons instead we
encorage everyone to either use /usr/bin/python2 /usr/bin/python3 rather then
/usr/bin/python, reverting the patch fixes it for you because then cmake looks
for /usr/bin/python first which is python2 rather then python3. It looks like
cmake rightly presumes that 3.6.4 is a higher number then 2.7.

>From reading FindPythonInterp I recommend you look at the following.

# The Python_ADDITIONAL_VERSIONS variable can be used to specify a list
# of version numbers that should be taken into account when searching
# for Python.  You need to set this variable before calling
# find_package(PythonInterp).

I suspect you just want to set that variable to 2.7 (you could list additional
python2 versions here as well if people are actually still using any others)