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

[Andrew Kuchling]

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?

(One thing to note is that "make clean" doesn't remove .so files from
the build/ tree, so if you did a make, then enabled zlib in
Modules/Setup and did "make clean ; make", the zlib.so is the build
tree would still be there.  Perhaps "make clean" should blow away the
build/ tree, even though that's inconsistent with what the clean
target does in Modules/.)

--amk