The dev-python/visual-5.72-r1 ebuild depends on unqualified dev-python/polygon. Polygon has two versions in the tree, 2.0.4 and 3.0.4, which are slotted because the former works only with Python 2 and the latter with Python 3. When emerging dev-python/visual, Portage pulls in the latest version, 3.0.4, regardless of the active Python version. In any case, Visual appears to be broken (as installed by Portage) for Python 3. On my system, in Python 3.2.2: >>> import visual Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/lib64/python3.2/site-packages/visual/__init__.py", line 1, in <module> from .visual_all import * File "/usr/lib64/python3.2/site-packages/visual/visual_all.py", line 1, in <module> from vis import version File "/usr/lib64/python3.2/site-packages/vis/__init__.py", line 3, in <module> from .cvisual import (vector, dot, mag, mag2, norm, cross, rotate, ImportError: dynamic module does not define init function (PyInit_cvisual) Perhaps dev-python/visual could have RESTRICT_PYTHON_ABIS="3.*" and depend on the dev-polygon:2 slot (at least for now)? Assuming Python 3 support gets fixed, I am not sure what to suggest to make the ebuild support Python 2 and/or 3 where the dependency slot for Polygon is contingent on the desired Python version (actually, the way Polygon is versioned seems a bit silly). Finally, is there a reason why Boost 1.48 is required? I had >=dev-libs/boost-1.41.0[python] in my overlay ebuild for dev-python/visual-5.72 and it seemed to work fine all the way back (for Python 2 at least).
dev-python/visual-5.72-r1 from Progress Overlay supports Python 3 properly and has correct dependencies. Ebuilds of Boost <1.48 don't have support for multiple Python ABIs.
See also http://archives.gentoo.org/gentoo-dev/msg_ab39d8366b714ecacfc7fa64cd48ad00.xml for details about Boost.
fixed, now visual depends on polygon:2. thanks
