On Fri, 2010-01-29 at 00:00 +0100, Adam wrote:
> Ronny Pfannschmidt wrote:
>
> > On Thu, 2010-01-28 at 18:11 +0000, Joan Miller wrote:
> > > 2010/1/28 holger krekel <hol...@merlinux.eu>:
> > > > On Wed, Jan 27, 2010 at 22:44 +0000, Joan Miller wrote:
> > > >> py.cleanup is very usefull, but it also would be usefull to delete the
> > > >> next directories (in bash would be):
> > > >>
> > > >> $ rm -rf ./build/ ./dist/ ./{src,lib}/*.egg-info
> > > >
> > > > i see how this can make sense. Any idea how/if this should
> > > > be made configurable? In my case *.egg-info as a general
> > > > to-be-removed pattern would make sense, i guess.
> > > I agree into a general pattern to delete the eggs info.
> > its actually more tricky, as setup.py develop needs them
>
> I think it is harmless, as distribute is going to delete the directory
> on setup.py clean:
>
the idea is not to break packages that got enabled within the users home
via setup.py develop --user
it does harm, as it would break features like entrypoints for those
> http://bitbucket.org/tarek/distribute/issue/122/setuppy-clean-should-delete-sourcestxt
>
> In the future it might be better to call setup.py clean on every
> setup.py instead of deleting the directory directly.
>
> --Adam
_______________________________________________
py-dev mailing list
py-dev@codespeak.net
http://codespeak.net/mailman/listinfo/py-dev
