Éric Araujo <mer...@netwok.org> added the comment: > Where was this fixed? It is still a problem in Python 2.6.6.
I assumed it was fixed after looking at the code: clean does take build-* options from the build command. > For example, if I do: > python setup.py build_ext --compiler=mingw32 build > --build-platlib=build\win64 > Then follow it up with: > python setup.py clean --build-base=build\win64 -a > This is what it does: > running clean > 'build\lib.win-amd64-2.6' does not exist -- can't clean it > removing 'build\bdist.win-amd64' (and everything under it) > 'build\scripts-2.6' does not exist -- can't clean it > As you can see, the base directory argument is ignored. I’m not sure if this is a distutils bug or if you have to use the same options (i.e. build-lib both times, not build-platlib then build-base). The original report used -b (build-base) for both commands, so I’ll turn that into a test (unless you’d like to do it?) to see if it works as intended or not. ---------- resolution: fixed -> stage: committed/rejected -> test needed status: closed -> open versions: -Python 2.5, Python 2.6, Python 2.7, Python 3.1, Python 3.2 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue818201> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com