Message150514
> 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. |
|
Date |
User |
Action |
Args |
2012-01-03 16:48:09 | eric.araujo | set | recipients:
+ eric.araujo, nicholas.riley, tarek, davidsj2 |
2012-01-03 16:48:09 | eric.araujo | set | messageid: <1325609289.77.0.301054523328.issue818201@psf.upfronthosting.co.za> |
2012-01-03 16:48:09 | eric.araujo | link | issue818201 messages |
2012-01-03 16:48:08 | eric.araujo | create | |
|