> > Try using the update-alternatives command so that "python" becomes > symbolically linked to python-3.4 rather than python-2.7.9 > > Or uninstall python 2.7.9. >
The standard Python distribution for versions 3 or greater installs a binary called `python3`, not `python`. That is the standard. If you are running Python3 from a binary called `python`, that is not standard. I know that distros do this (or can do it with tweaking); but that doesn't make it standard. If you want to be sure you're getting Python3, you should look for a binary called `python3`. Does FindPython not have logic to check the versioned pythonx.y > alternatives when doing these checks? Why isn't it checking the python3 > and python3.x commands in this circumstance? Have you tried the FindPython I referenced above? It would solve the problems you brought to this thread (and maybe even some you didn't yet know you have).
-- Powered by www.kitware.com Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ Kitware offers various services to support the CMake community. For more information on each offering, please visit: CMake Support: http://cmake.org/cmake/help/support.html CMake Consulting: http://cmake.org/cmake/help/consulting.html CMake Training Courses: http://cmake.org/cmake/help/training.html Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html Follow this link to subscribe/unsubscribe: http://public.kitware.com/mailman/listinfo/cmake
