Clean after updating with git.

[mvaled]

If the repo your working with removes a python module, mr.developer leaved .pyc files behind. This may hurt your ability to test that other modules are properly updated (by not importing the removed module).

[fschulze]

I think this is a bad idea. The options you use remove all untracked files. It might make sense when always-checkout is set to force, but I'm not sure of that either. Adding -- *.pyc to the options might be fine.

[mvaled]

Yes. It would make more sense when always-checkout is set to force. My use case is for deployments: I have some packages which are not published in the PyPI (nor we keep an internal one, cause the overhead of maintaining would be of no benefit). Development .cfg files have always-checkout=no, but production development conf files do have it set to force.

In any case, we can also put another option: clear-after-update it could be either: no, all or a pattern passed to git clean. What do you think?

[mauritsvanrees]

Removing pyc files would be okay, the rest not.

I don't really consider it the job of mr.developer to handle this. It is more an unfortunate side effect of how git and Python work.

A practical approach outside or mr.developer would be to add a buildout part that does a cleanup in the checkouts. I have a remove-cruft script that I sometimes run to cleanup old pyc/pyo files:

#! /bin/sh
find . -name '*.pyc' -o -name '*.pyo' -o -name '*~' | xargs rm

[mvaled]

A practical approach outside or mr.developer would be to add a buildout part that does a cleanup in the checkouts. I have a `remove-cruft` script that I sometimes run to cleanup old pyc/pyo files: ``` #! /bin/sh find . -name '*.pyc' -o -name '*.pyo' -o -name '*~' | xargs rm ```

The problem would be to determine which dirs to affect. I'm going to change the PR to affect only 'pycs' and 'pyos'.