(please cc me on any replies - i'm not on the distutils sig) Am I missing something or is "python setup.py clean" only a feeble attempt at cleaning what was created by distutils? If I execute python setup.py build python setup.py clean python setup.py build the second build does nothing, claiming that everything is up-to-date. In my opinion, the clean command should delete the entire build subdirectory, not just the build/temp.<arch> directory. Thx, -- Skip Montanaro (skip@pobox.com - http://www.mojam.com/)
Skip Montanaro wrote:
(please cc me on any replies - i'm not on the distutils sig)
Am I missing something or is "python setup.py clean" only a feeble attempt at cleaning what was created by distutils? If I execute
python setup.py build python setup.py clean python setup.py build
the second build does nothing, claiming that everything is up-to-date. In my opinion, the clean command should delete the entire build subdirectory, not just the build/temp.<arch> directory.
Agreed. Basically, "clean" should be the same as "clean --all" is now. I'd also like a "distclean" command which not only removes the build/ dir, but also the dist/ dir and any funny files which may exist in the base dir such as *~, *.bak, *.pyc, *.pyo, etc. -- Marc-Andre Lemburg CEO eGenix.com Software GmbH ______________________________________________________________________ Company & Consulting: http://www.egenix.com/ Python Software: http://www.egenix.com/files/python/
participants (2)
-
M.-A. Lemburg -
Skip Montanaro