Re: [python-committers] autoconf 2.70

2016-11-23 Thread Xavier de Gaye
On 11/23/2016 11:49 PM, Gregory P. Smith wrote: > I do not think we should require individual developers committing changes to configure.ac to use a particular version of autoconf when regenerating configure. That is a burden. I do not agree, configure is a file tracked in

Re: [python-committers] autoconf 2.70

2016-11-23 Thread Martin Panter
>> On 11/22/2016 08:16 PM, Ned Deily wrote: >> > On Nov 22, 2016, at 11:06, Xavier de Gaye wrote: >> >> The configure file on the default and 3.6 branches have been generated >> >> with autoconf 2.70 once again. This is annoying when you have to >> >> maintain patches to this configure file in

Re: [python-committers] autoconf 2.70

2016-11-23 Thread Victor Stinner
2016-11-23 23:49 GMT+01:00 Gregory P. Smith : > The solution to your problem is to maintain your patches _only_ against > configure.ac and rerun autoconf using whatever version you need yourself. I agree :-) Victor ___ python-committers mailing list pyt

Re: [python-committers] autoconf 2.70

2016-11-23 Thread Gregory P. Smith
I do not think we should require individual developers committing changes to configure.ac to use a particular version of autoconf when regenerating configure. That is a burden. The solution to your problem is to maintain your patches _only_ against configure.ac and rerun autoconf using whatever ve