Summary: | dev-python/feedparser-5.1 - python3.2 setup.py build -b build: ImportError: No module named setuptools | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Mark Nowiasz <mark+gentoobugs> |
Component: | [OLD] Development | Assignee: | Python Gentoo Team <python> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | djqfrey |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | build.log |
Description
Mark Nowiasz
2012-02-25 06:13:09 UTC
Created attachment 303121 [details]
build.log
build.log
Could not replicate; localhost dev-python # e Available Python interpreters: -------------------------------- [3] python2.7 [4] python3.1 * [5] python3.2 localhost dev-python # emerge gwibber >>> Emerging (1 of 9) dev-python/gnome-python-desktop-base-2.32.0 >>> Emerging (2 of 9) dev-python/python-distutils-extra-2.31 from progress >>> Emerging (3 of 9) dev-python/feedparser-5.1 --------------------------------------------------------- >>> Installing (3 of 9) dev-python/feedparser-5.1 localhost dev-python # e5 (eselect python set 5) python-3.2 globally localhost dev-python # emerge feedparser ------------------------------------------------- >>> Verifying ebuild manifests >>> Emerging (1 of 1) dev-python/feedparser-5.1 >>> Jobs: 0 of 1 complete, 1 running Load avg: 0.22, 0.40, >>> Installing (1 of 1) dev-python/feedparser-5.1 In the ebuild DEPEND="dev-python/setuptools" I don't know what you've done but it's pretty cunning. It's not a progress overlay dev-python/feedparser-5.1. Only thing not retried out is your eselected python and the ebuilds should take of that as well. Most odd Hmm, I haven't got python 3.1 installed and python 2.7 selected: eselect python list Available Python interpreters: [1] python2.7 * [2] python3.2 Might this be the problem? well no, The problem seems to be that setuptools hasn't been installed into the python3.2 dir under site-packages. I would think if you eselected python3.2 and emerged setuptools, then emerged feedparser it will be happy. Holes like this the python team would prefer to close (In reply to comment #4) > well no, The problem seems to be that setuptools hasn't been installed into > the python3.2 dir under site-packages. I would think if you eselected > python3.2 and emerged setuptools, then emerged feedparser it will be happy. > Holes like this the python team would prefer to close Yes, that did the trick - eselecting python to 3.2, emerge -1 setuptools and changing back to 2.7, now it's compiling just fine. Mark: I suggest you run python-updater to ensure that your python modules are installed consistently for both of your installed versions of python. *** Bug 434836 has been marked as a duplicate of this bug. *** |