Summary: | dev-python/pyudev-0.16.1 with python-3.3 - python3.3 setup.py build -b build-3.3: ImportError: No module named 'setuptools' | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Robert Cabrera <robcab666> |
Component: | [OLD] Development | Assignee: | Python Gentoo Team <python> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | python |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | pyudev-0.16.1.build.log |
Description
Robert Cabrera
2013-05-23 22:51:40 UTC
* The complete build log is located at '/var/tmp/portage/dev-python/pyudev-0.16.1/temp/build.log'. Please attach the entire build log to this bug report. Created attachment 349106 [details]
pyudev-0.16.1.build.log
added build.log
I think I see the issue now. The problem lies with setuptools. I just re-emerged it and got this message: * Messages for package dev-python/setuptools-0.6.40: * Building package for python3.2 only while python3.3 is active. * Please consider switching the active Python 3 interpreter: * * eselect python set --python3 python3.2 * * Please note that after switching the active Python interpreter, * you may need to run 'python-updater' to rebuild affected packages. * * For more information on python.eclass compatibility, please see * the appropriate python-r1 User's Guide chapter [1]. * * [1] http://www.gentoo.org/proj/en/Python/python-r1/user-guide.xml#doc_chap2 >>> Auto-cleaning packages... It seems obvious now that python-3.3 isn't ready yet. There are probably other packages that aren't compatible with it too. I'm going to mask and uninstall it. I run a system that already has quite a few cutting edge "testing" apps, compilers, and libraries. This is just an extra headache. I'll just wait until 3.3 is ready for prime-time. TIA You are just running into an interaction between the old python.eclass and the new python-r1.eclass. You need to update PYTHON_TARGETS in make.conf to include python3_3. For example: PYTHON_TARGETS="python2_7 python3_2 python3_3" This will cause setuptools (a python-r1 based ebuild) to be installed for all 3 python versions. Once pyudev is migrated to python-r1.eclass, this will be enforced with a dependency which we cannot currently express with python.eclass. 0.20.0 should have this fixed |