Is setup.py a "good thing"? (long)

Gerd Woetzel woetzel at gmd.de
Fri Mar 23 11:08:30 EST 2001


Andrew Kuchling <akuchlin at mems-exchange.org> writes:

>If a module is enabled in Modules/Setup, then setup.py won't try to
>build it, so you could just enable Tkinter there with whatever options
>are required.

Hmm, maybe that's true for Tkinter. With socket an zlib I had some
Problems on SunOS 5.8.

I need to load libssl.so and libz.so from a special place.
Hence I used Modules/Setup. Make went well, all tests passed.

However after installing, python2.1 did not load these libs anymore :(.

What happened?

Modules/Setup has buit zlibmodule.so and socketmodule.so which worked
fine during the test phase, but setup.py has (secretly?) created
zlib.so (socket.so) too! Finally "make install" has installed all of them.

Of course, python selcts between xxx.so and xxxmodule.so according to
murphey's law <oops-wink>. 

Yes, it was easy to remove the wrong libs from lib/python21 in the end.
However, I was quite confused for some time. 
--
Gerd Woetzel            | email: gerd.woetzel at gmd.de
GMD FIT.CSCW            | phone: ++49 2241 142648 (fax: 142084)
D-53754 Sankt Augustin  | www:   http://orgwis.gmd.de/~woetzel/



More information about the Python-list mailing list