Gaetano Mendola wrote:
> Joe Conway wrote:
>> I wasn't going to -- python's own docs say I shouldn't need to. From
>> the link above:
>>
>> "the Distutils work just fine with Python 1.5.2, and it is reasonable
>> (and expected to become commonplace) to expect users of Python 1.5.2
>> to download and install the Distutils separately before they can
>> install your modules"
>
> I'm not native english speakers but that sentence above doesn't imply
> Python 1.5.2 => Distutils. So instead of an error like this:
>
> checking Python installation directories... Traceback (innermost last):
> File "<string>", line 1, in ?
> ImportError: No module named distutils
> Traceback (innermost last):
> File "<string>", line 1, in ?
> ImportError: No module named distutils
> /usr/
> checking how to link an embedded Python application... no
> configure: error: Python Makefile not found
> error: Bad exit status from /var/tmp/rpm-tmp.56347 (%build)
>
> is better have:
>
> Error: you need to have Distutil installed
Perhaps. The first error message seems clear enough to me, but if you
want to send me the necessary distutils test, I can incorporate it. Any
other opinions out there?
Joe
