rRnning "python setup.py clean" says:

% python setup.py 
clean
running clean
removing 'build/temp.linux-i686-2.2' 
(and everything under it)

However, following that with an 
immediate "python
setup.py build" reports:

% python 
setup.py build
running build
running build_py
not copying 
RSWM/__init__.py (output up-to-date)
running 
build_ext
skipping 'rswm' extension (up-to-date)

Shouldn't 
the "clean" command simply delete the build
directory?

Logged In: YES 
user_id=6656

Hmm.  Does "python setup.py clean --all" do what you
want/expect?

Agree this should possibly be the default, by analogy with
"make clean".

Logged In: YES 
user_id=11375

"make clean" usually deletes intermediate files such as 
.o files, leaving executables such as the 'python' 
binary 
in place.  This means you can run it to save disk space 
after building something, and the Distutils 'clean' 
command probably leaves the .so files alone to match 
this behaviour.  Also, note that Modules/Makefile only 
deletes .so files on a "make clobber" (but "make clean" 
deletes the Python executable).

Logged In: YES 
user_id=31392

I think the reported behavior is intended, so I'm closing
the bug report.