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

[Martin von Loewis]

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

> woetzel at gmd.de (Gerd Woetzel) writes:
> > 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.
> 
> That certainly shouldn't have happened.  Can you reproduce the problem?

It could happen if you use *shared* in Modules/Setup and if setup.py
is older than 1.30; before, it would use on builtin_module_names to
exclude modules. So that was a problem once and should be fixed since
2.1b1.

Regards,
Martin