Created attachment 328364 [details] build.log from dev-python/argparse In order to test my programs across different python versions, I recented added this to my /etc/portage/make.conf: PYTHON_TARGETS="python2_6 python2_7 python3_2 pypy1_8 pypy1_9" (grumble that I'll have to change it again when 3.3 get stabilized - I don't want system packages to fail because of possible 3.3 compatibility issues) Then I did a full update of world and ran python-updater. (Is python-updater even meaningful for packages that support PYTHON_TARGETS, since that gets caught by emerge --newuse?) However, dev-python/setuptools only builds for the currently eselect'ed versions - python2.7 and python3.2. An example of a package that fails to build is dev-python/argparse, build.log attached. Although there *has* been some churn in argparse lately - there's now virtual/argparse, which correctly does nothing for versions of python where it's included in the standard library (since 2.7) - the bug is obviously in setuptools. (During the same set of updates there was a problem with dev-python/pythonmagick, but I don't know if it's related so I'll wait for this bug to be fixed.) $ emerge -pv dev-python/setuptools dev-python/argparse [ebuild R ] dev-python/setuptools-0.6.30 0 kB [ebuild U ] dev-python/argparse-1.2.1-r1 [1.2.1] PYTHON_TARGETS="pypy1_8%* pypy1_9%* python2_6%* python2_7%* python3_2%* -jython2_5% -python2_5% -python3_1% (-python3_3)" 0 kB
Can you please post the results of `emerge --info` in a comment?
I guess it's time to migrate setuptools as well.
Ok, -r1 should fix it.
