GNOME Bugzilla – Bug 688062
add py3cairo to the 3.8 modulesets
Last modified: 2012-11-14 22:00:39 UTC
as we are porting things to python3, we will need it as a dependency. <waf id="py3cairo"> <pkg-config>py3cairo.pc</pkg-config> <branch module="releases/pycairo-1.10.0.tar.bz2" version="1.10.0" repo="cairo.org" hash="sha256:9aa4078e7eb5be583aeabbe8d87172797717f95e8c4338f0d4a17b683a7253be" size="246556"/> <dependencies> <dep package="cairo"/> </dependencies> </waf> is what I tried to add next to py2cairo, but unfortunately, it doesn't work. The waf script finds the wrong python (/usr/bin/python), and the only way to tell it to use python3 seems to be setting PYTHON=python3 in the environment - which jhbuild doesn't let me do :-(
Created attachment 228734 [details] [review] waf: add support for a python-command attribute, useful for Python 3.
Created attachment 228735 [details] [review] 3.8: add py3cairo (pyobject dependency)
Created attachment 228736 [details] [review] 3.8: add py3cairo (pygobject dependency)
Review of attachment 228736 [details] [review]: Thank you, looks good to commit. There is still some work to be done. I'd expect this to work: # jhbuild run python3 -c "import cairo" Traceback (most recent call last):
+ Trace 231175
from _cairo import *
PYTHONPATH is wrong.
It would have been much easier if Python 3 had a different environment variable (looks like that was discussed in <http://bugs.python.org/issue2375>); actually I don't know, I have no idea how we're supposed to get both python versions to behave properly.
(In reply to comment #5) > It would have been much easier if Python 3 had a different environment variable > (looks like that was discussed in <http://bugs.python.org/issue2375>); actually > I don't know, I have no idea how we're supposed to get both python versions to > behave properly. I raised a new bug for this. See bug 688353.