On Jul 18, 2006, at 11:32 AM, Phillip J. Eby wrote: > At 10:57 AM 7/18/2006 -0700, Bob Ippolito wrote: > >> On Jul 18, 2006, at 10:42 AM, Phillip J. Eby wrote: >> >>> At 10:11 AM 7/18/2006 -0700, Bob Ippolito wrote: >>> >>>> On Jul 18, 2006, at 9:04 AM, Phillip J. Eby wrote: >>>> >>>>> At 04:29 PM 7/17/2006 -0700, Bob Ippolito wrote: >>>>>> On Jul 17, 2006, at 4:17 PM, Phillip J. Eby wrote: >>>>>>> If you can live with that limitation (explicitly setting one or >>>>>>> both of those options when making a super call), I can have it >>>>>>> respect extra_path. But it's a no-go in any other circumstance, >>>>>>> I'm afraid. >>>>>> >>>>>> I don't have any problem explicitly setting either or both of >>>>>> those >>>>>> options. I'm only targeting setuptools, I don't care about old >>>>>> distutils compatibility... I just want something close to the old >>>>>> behavior, for now. >>>>> >>>>> Okay, it's in the 0.7 and 0.6 SVN trunks now; please test >>>>> (ez_setup.py setuptools=dev06) and let me know if it works for >>>>> you. >>>> >>>> seems to work, thanks! >>>> >>>> -bob >>> >>> Great; please check out the sdist/egg_info version thing too. >> >> Looks right, I tried both a release and dev configuration and it >> preserved the right metadata in setup.cfg. I have not tried a >> setup.cfg that had any other settings in it though. > > I've tested it with that (by building sdists of setuptools) and it > works. The code that's used to edit setup.cfg is the same that's > used by "setopt" and "saveopts", so it's had some prior testing for > that aspect anyway. I was mainly wanting to make sure that > building sdists created this way works properly. > > Oh, actually, the specific thing I wanted to make sure of was that > on platforms with hard linking available it 1) works correctly and > 2) doesn't modify the original setup.cfg. The "sdist" command can > create an archive tree using hard linking, so I included some code > to work around that, but it doesn't execute on Windows so I can't > test it in anger, so to speak, and haven't had a moment yet to > check it out on a Linux box. If you have a setup.cfg, it should > delete the one in the temporary build tree and then recopy it from > the source, before editing it.
Mac OS X supports hard linking, and I did not see any of my setup.cfg files change while I was testing... so it seems it did what it was supposed to do without any ill side-effects. -bob _______________________________________________ Distutils-SIG maillist - [email protected] http://mail.python.org/mailman/listinfo/distutils-sig
