[Distutils] Wrong depedencies in install_lib command?
patrick.gerken at googlemail.com
Fri Feb 13 10:59:07 CET 2009
On Wed, Feb 11, 2009 at 20:17, P.J. Eby <pje at telecommunity.com> wrote:
> At 08:06 PM 2/11/2009 +0100, Patrick Gerken wrote:
>> i tried to install reportlab via easy_install, which always failed while
>> compiling some c-modules.
>> Installing it via setup.py install worked flawlessly
>> After a while, I found the difference.
>> setup.py install calls the command _build_, which calls _build_clib_ and
>> then _build_ext_
>> easy_install calls _bdist_egg_, which calls _install_lib_, which calls
>> _build_ext_ WITHOUT calling _build_clib_.
>> The module docstring of the command build_clib mentions, that these
>> libraries can be a dependency to build_ext, so I patched install_lib.py to
>> call build_clib too, and now I can easy_install the newest reportlab!
>> If anybody wants to reproduce the behaviour, I added my patch, which I did
>> against the current trunk of distutils/command/install_lib.py
>> I made a relative patch so to patch the file. you have to go into this
>> directory and call
>> patch install_lib.py dependency.patch
>> Does this qualify as a bug in the bugtracker?
> Yes, definitely. It'd be nice to have a setuptools patch to workaround the
> problem as well.
I feel a bit uneasy about this kind of stuff, because of potential side
effects I am not aware of. Would it be fine to call the command _build_
after the command _egg_info_ in _bdist_egg_ ? That would call the other
commands in the right order.
I added a ticket, but I am still not finished writing the test case. I will
add one, hopefully during the weekend
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Distutils-SIG