Message88651
| Author |
purpleidea |
| Recipients |
pitrou, purpleidea, r.david.murray, tarek |
| Date |
2009年06月01日.16:07:40 |
| SpamBayes Score |
3.486693e-07 |
| Marked as misclassified |
No |
| Message-id |
<1243872463.36.0.573063957565.issue6142@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
I could agree with R. David Murray, and I think that it's fine that this
be included under a dist clean command.
Ultimately I'm writing an application and I'm trying to use distutils
with it. I'll potentially run a: "$ setup.py build_ext -i" or whatever
it may be, and then I'll want to get rid of all the mess. So I'll want
to run a clean. If that clean won't get rid of .pyc for me in one
command, then i have to run a second shell script to clean my dir,
instead of sticking the two together. Which is why i think a clean --pyc
option is useful (off by default) and which I can easily enable in
setup.cfg with [clean] pyc=1
I think this is harmless. Anyone agree?
thanks!
_J |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2009年06月01日 16:07:43 | purpleidea | set | recipients:
+ purpleidea, pitrou, tarek, r.david.murray |
| 2009年06月01日 16:07:43 | purpleidea | set | messageid: <1243872463.36.0.573063957565.issue6142@psf.upfronthosting.co.za> |
| 2009年06月01日 16:07:41 | purpleidea | link | issue6142 messages |
| 2009年06月01日 16:07:40 | purpleidea | create |
|