[Distutils] I wonder what is the best practice to clean a buildout project ?

Marius Gedminas marius at pov.lt
Thu Jan 31 19:52:22 CET 2013


On Thu, Jan 31, 2013 at 03:37:21PM +0100, Stéphane Klein wrote:
> I wonder what is the best practice to clean a buildout project ?
> 
> I would like a command to remove :
> 
> * bin/
> * develop-eggs
> * parts
> * .installed.cfg
> 
> I can create a Makefile clean, or clean.sh script.
> 
> What do you do in your project ?

I usually create a Makefile with rules to 'make run', 'make test' and so
on, as appropriate (and a plain 'make' to build a local virtualenv for
isolation, bootstrap bin/buildout with it, and run bin/buildout
whenever buildout.cfg or versions.cfg or my setup.py changes).

I've never found the need to 'make clean' a buildout project, but if I
did, I'd add a makefile rule.

Marius Gedminas
-- 
WARN_(accel)("msg null; should hang here to be win compatible\n");
        -- WINE source code
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: Digital signature
URL: <http://mail.python.org/pipermail/distutils-sig/attachments/20130131/88675549/attachment.pgp>


More information about the Distutils-SIG mailing list