>=dev-python/pycairo-1.8.4 supports only Python >=2.6. dev-python/pycairo belongs to dependencies of dev-python/pygtk. When dev-python/pygtk has been built for Python <2.6, then importing gtk fails in these versions of Python. $ python2.5 -c 'import gtk' Traceback (most recent call last): File "<string>", line 1, in <module> File "/usr/lib64/python2.5/site-packages/gtk-2.0/gtk/__init__.py", line 40, in <module> from gtk import _gtk ImportError: No module named cairo $ I suggest to work around this problem by requiring Python >=2.6 in >=dev-python/pygtk-2.16.0.
that's a known bug of pretty much all gnome python modules, see bug #262241. The work around is to have only one python installed and run python-updater to make sure all gnome modules are built against the available python. *** This bug has been marked as a duplicate of bug 262241 ***
(In reply to comment #1) Actually it's a different problem. When Python 2.5 is the only installed version of Python, then it is impossible to build >=dev-python/pycairo-1.8.4 and all its non-optional reverse dependencies like dev-python/pygtk. This problem can be fixed after deletion of <dev-python/pycairo-1.8.4.
Wait. >=pycairo-1.8.4 depends on python-2.6, so you cannot have it installed with only 2.5. Since gnome only supports one python version, you will need to have everything built against 2.6 in order to have 1.8.4. Right?
(In reply to comment #3) > >=pycairo-1.8.4 depends on python-2.6, so you cannot have it installed > with only 2.5. Yes. My suggestion was to prevent some minor problems when e.g. both 2.5 and 2.6 are installed. > you will need to have everything built against 2.6 in order to have 1.8.4. Yes. GNOME Python modules will have to restrict <2.6 to avoid breaking ABI dependency graph (noticeable with EAPI >= 4).
<dev-python/pycairo-1.8.4 is no longer in the tree, so I have disabled support for Python <2.6 in dev-python/pygtk-2.16.0-r1.
