>>> Install paver-1.0.3 into /var/tmp/portage/dev-python/paver-1.0.3/image/ category dev-python * Installation of dev-python/paver-1.0.3 with CPython 2.7... python2.7 setup.py build -b build-2.7 install --root=/var/tmp/portage/dev-python/paver-1.0.3/image/ --no-compile running build running build_py warning: build_py: byte-compiling is disabled, skipping. running build_scripts running install Traceback (most recent call last): File "setup.py", line 7, in <module> paver.tasks.main() File "paver-minilib.zip/paver/tasks.py", line 621, in main File "paver-minilib.zip/paver/tasks.py", line 604, in _launch_pavement File "paver-minilib.zip/paver/tasks.py", line 569, in _process_commands File "paver-minilib.zip/paver/setuputils.py", line 146, in __call__ File "/usr/lib64/python2.7/distutils/dist.py", line 970, in run_command cmd_obj = self.get_command_obj(command) File "/usr/lib64/python2.7/distutils/dist.py", line 856, in get_command_obj self._set_command_options(cmd_obj, options) File "/usr/lib64/python2.7/distutils/dist.py", line 899, in _set_command_options % (source, command_name, option)) distutils.errors.DistutilsOptionError: error in command line: command 'install' has no such option 'no_compile' * ERROR: dev-python/paver-1.0.3 failed: * Installation failed with CPython 2.7 in distutils_installation() function
Created attachment 256163 [details] emerge --info
Created attachment 256165 [details] build log
I couldn't reproduce this with 2.7.1. Anyone else?
paver not emerging caused python-updater to abort. Now I've unmerged paver, run python-updater over the majority of my python package, and was able to remerge paver afterwards. So it seems that this was due to some kind of inconsistency in my python setup, due to the migration from 2.6 to 2.7. My guess would be setuptools. Could it be paver should DEPEND on setuptools?
I have added dependency on setuptools, but lack of this dependency wouldn't cause your problem (python-updater doesn't check dependencies).
(In reply to comment #5) > I have added dependency on setuptools, but lack of this dependency wouldn't > cause your problem (python-updater doesn't check dependencies). The way I see it, python-updater passed all python packages to portage, and portage ordered them by dependency, but didn't order setuptools before paver. As a consequence, paver failed to built, as setuptools wasn't there for python 2.7. And when emerge failed, python-updater aborted as well. Then I unmerged paver, ran the updater, got setuptools updated among others, and then paver was happy as well. Just guessing, though.
