I have Python 3 and Python 2 installed next to each other. As the installation guide suggest, I run waf as follows: $ python3 ./waf configure with the following result: ./options() Setting top to : /home/evertr/Downloads/pycairo-1.10.0 Setting out to : /home/evertr/Downloads/pycairo-1.10.0/build_directory ./configure() Checking for 'gcc' (c compiler) : ok Checking for program python : /usr/bin/python python executable '/usr/bin/python' different from sys.executable '/data/evertr/sw/bin/python3' Checking for python version : (2, 6, 6, 'final', 0) The python version is too old, expecting (3, 1, 0) (complete log in /home/evertr/Downloads/pycairo-1.10.0/build_directory/config.log) Along the way, waf appears to ignore my specified Python 3 version, and decides to simply pick up the system installed one.
The way to specify the python version in waf is through an environment variable. The version used to run waf itself is unrelated. Example: PYTHON=python3.3 ./waf configure
Since 1.11 pycairo uses distutils for building. There is a good chance that this bug no longer occurs with the new system. If there are still problems please file a bug: https://github.com/pygobject/pycairo/issues
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.