As I suspected there's a bug in the current distutils code. Steps to reproduce the problem:
1: Run "python setup.py sdist --formats=gztar,tar". 2. dist directory now contains "module.gztar" and "module.tar" files as expected. 3: Run "python setup.py sdist --formats=tar,gztar". 4. dist directory now contains only "module.gztar" file because "module.tar" has been overwritten when archive_util.make_tarball() function was called for the second time. I'll try to fix this while I'm working on the other issue. 2008/1/19, Giampaolo Rodola' <[EMAIL PROTECTED]>: > > The other argument for using spawn() first would be that it's the > > least invasive and most backward-compatible change. > > Yeah, I agree. It would be probably better using spawn() as default. > > 2008/1/19, Phillip J. Eby <[EMAIL PROTECTED]>: > > At 08:10 PM 1/19/2008 +0100, Giampaolo Rodola' wrote: > > >Just another thing. > > >I was wondering what do you think would be better to do as default. > > >Using Python modules as default and spawn() as fall back or doing > > >the contrary? > > >Maybe using spawn() as default would be better since original > > >utilities should be faster than python modules. > > > > I suppose that's a possibility, although the tarfile module doing the > > compression might be faster than separate tar and compress steps. > > > > The other argument for using spawn() first would be that it's the > > least invasive and most backward-compatible change. > > > > > _______________________________________________ Distutils-SIG maillist - [email protected] http://mail.python.org/mailman/listinfo/distutils-sig
