Home → Problems →

CMake can no longer find Python 2/3

• Edit

Zeex

07 Apr, 2015 10:23 PM

It seems that somtehing have changed in the Python installation, not sure what, but CMake can no longer find the Python interpreter. I always get this error:

CMake Error at C:/Program Files (x86)/CMake/share/cmake-3.1/Modules/FindPackageHandleStandardArgs.cmake:138 (message):
  Could NOT find PythonInterp: Found unsuitable version "1.4", but required
  is at least "2.7" (found C:/Python27/python.exe)

1.4 means that CMake was not able to determine the version of Python. When I tried to do the same by running 'C:\Python27\python.exe -c "import sys; sys.stdout.write(sys.version)"' I got this:

  File "C:\Python34\lib\site.py", line 176
    file=sys.stderr)
        ^
SyntaxError: invalid syntax

Exactly the same errors popped up when chocolatey was installing pip (the python package manager):

easy.install v0.6.11.4
PATH environment variable does not have C:\Python34 in it. Adding...
PATH environment variable does not have C:\Python34\Scripts in it. Adding...
Setting PYTHONHOME environment variable to 'C:\Python34'
PS: PYTHONHOME variable is not required to Python works, but it is a good practice to have it.
Using python home at 'C:\Python34'
Installing easy_install for Python(2.7.9)...
Installing setuptools from http://pypi.python.org/pypi/setuptools ...
Downloading easy.install 32 bit
  from 'http://peak.telecommunity.com/dist/ez_setup.py'
Running python file: 'C:\Users\appveyor\AppData\Local\Temp\ez_setup.py'
  File "C:\Python34\lib\site.py", line 176
    file=sys.stderr)
        ^
SyntaxError: invalid syntax

It seems like it installs easy setup for Python 2.7 with Python 3.4, which is kind of messed up.

1. Support Staff 1 Posted by Feodor Fitsner on 07 Apr, 2015 11:20 PM

   

   It was Python 2.7.9 installed to the same location C:\Python27 (http://www.appveyor.com/updates/2015/04/04) - we were sending notification on Saturday (you can subscribe/unsubscribe on https://ci.appveyor.com/profile page). I'm not sure what that error means or is there any breaking changes in 2.7.9 making it unsuitable for CMake, but PATH still has the same original C:\Python27 location. If you have an idea what might cause this error or missing/outdated on build workers please let me know so we could fix the environment.

   • Edit

2. Support Staff 2 Posted by Feodor Fitsner on 07 Apr, 2015 11:35 PM

   

   What build worker image do you use?

   I've got this result for default image on both Azure and Pro environments:
   https://ci.appveyor.com/project/FeodorFitsner/simple-console/build/...

   • Edit

3. 3 Posted by Zeex on 08 Apr, 2015 02:29 AM

   

   Here are two builds for comparison, one worked fine and the other one failed (both had the same appveyor.yml):

   https://ci.appveyor.com/project/Zeex/sampgdk/build/122/job/71vsgq5b6lo2dkgj
   https://ci.appveyor.com/project/Zeex/sampgdk/build/123/job/9mye8dvu6w3nhco8

   The only difference that I could spot is Python 2.7 had been already installed in the second (failed) build.

   I've kind of fixed this temporarily by adding C:\Python27\Scripts to PATH instead of installing pip (Python now ships with pip.exe, but it's not in PATH after installation). I guess it's a bug in the pip package from chocolatey, I'll do some more research.

   • Edit

4. Support Staff 4 Posted by Feodor Fitsner on 08 Apr, 2015 02:43 AM

   

   Why would you need installing Python and CMake if they are already installed on build machine?

   - Feodor

   • Edit

5. 5 Posted by Zeex on 08 Apr, 2015 08:01 AM

   

   Well, you know, just in case... Actually installing python2 used to be helping me to fix some other error, can't remember which exactly right now.

   • Edit

6. Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 01:55 AM.