Re: [Python-Dev] SSL support in _socket
barry@zope.com (Barry A. Warsaw) writes:
It shouldn't have been this difficult to debug. Surely there must be some way to tell setup.py not to delete .so's it can't import so we have a prayer of finding the real problems.
Maybe it just shouldn't install the shared libs if they fail to import? Cheers, M. -- It's actually a corruption of "starling". They used to be carried. Since they weighed a full pound (hence the name), they had to be carried by two starlings in tandem, with a line between them. -- Alan J Rosenthal explains "Pounds Sterling" on asr
Michael Hudson wrote:
barry@zope.com (Barry A. Warsaw) writes:
It shouldn't have been this difficult to debug. Surely there must be some way to tell setup.py not to delete .so's it can't import so we have a prayer of finding the real problems.
Maybe it just shouldn't install the shared libs if they fail to import?
I'm not sure why setup.py is trying to be smart in the first place. A warning is certainly a good idea, but then setup.py should let the user decide what to do about the problem, IMHO. -- Marc-Andre Lemburg CEO eGenix.com Software GmbH ______________________________________________________________________ Company & Consulting: http://www.egenix.com/ Python Software: http://www.egenix.com/files/python/
"MH" == Michael Hudson <mwh@python.net> writes:
>> It shouldn't have been this difficult to debug. Surely there >> must be some way to tell setup.py not to delete .so's it can't >> import so we have a prayer of finding the real problems. MH> Maybe it just shouldn't install the shared libs if they fail MH> to import? That would be an improvement because at least there'd be an artifact you can poke at after the build process is complete. -Barry
participants (3)
-
barry@zope.com
-
M.-A. Lemburg
-
Michael Hudson