Re: [Python-Dev] [Python-checkins] r85486 - python/branches/py3k/configure

2010-10-14 Thread Martin v. Löwis
> Is it possible to pin the autoconf version (not just floor it)? Not that I know of, no. > Should we appoint an autoconf BDFL who can commit changes after configure.in > is changed? Most recently, it was between me and Benjamin most of the time, and that seems to have worked fine. Now Benjami

Re: [Python-Dev] [Python-checkins] r85486 - python/branches/py3k/configure

2010-10-14 Thread Barry Warsaw
On Oct 14, 2010, at 09:11 PM, Martin v. Löwis wrote: >> I don't see it as any more of a problem than upgrading against other >> dependencies (like gcc?). > >Ok, so let's drop the requirement then. Good for me. Is there a place where this requirement is documented? -Barry signature.asc Descrip

Re: [Python-Dev] [Python-checkins] r85486 - python/branches/py3k/configure

2010-10-14 Thread Martin v. Löwis
> I don't see it as any more of a problem than upgrading against other > dependencies (like gcc?). Ok, so let's drop the requirement then. Regards, Martin ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-d

Re: [Python-Dev] [Python-checkins] r85486 - python/branches/py3k/configure

2010-10-14 Thread Benjamin Peterson
2010/10/14 "Martin v. Löwis" : >>> I think it was intentional (at least deliberate), but I think it is a >>> problem and should be reverted. There is, at any point, the official >>> version that Python uses for autoconf, which at the moment is 2.65. >>> The rationale is that with changing autoconf

Re: [Python-Dev] [Python-checkins] r85486 - python/branches/py3k/configure

2010-10-14 Thread Martin v. Löwis
>> I think it was intentional (at least deliberate), but I think it is a >> problem and should be reverted. There is, at any point, the official >> version that Python uses for autoconf, which at the moment is 2.65. >> The rationale is that with changing autoconf versions, the actual >> configure s

Re: [Python-Dev] [Python-checkins] r85486 - python/branches/py3k/configure

2010-10-14 Thread Barry Warsaw
On Oct 14, 2010, at 08:27 PM, Martin v. Löwis wrote: >I think it was intentional (at least deliberate), but I think it is a >problem and should be reverted. There is, at any point, the official >version that Python uses for autoconf, which at the moment is 2.65. >The rationale is that with changin

Re: [Python-Dev] [Python-checkins] r85486 - python/branches/py3k/configure

2010-10-14 Thread Benjamin Peterson
2010/10/14 "Martin v. Löwis" : > Am 14.10.2010 19:57, schrieb Daniel Stutzbach: >> On Thu, Oct 14, 2010 at 12:38 PM, barry.warsaw >> mailto:python-check...@python.org>> wrote: >> >>     -# Generated by GNU Autoconf 2.65 for python 3.2. >>     +# Generated by GNU Autoconf 2.67 for python 3.2. >> >>

Re: [Python-Dev] [Python-checkins] r85486 - python/branches/py3k/configure

2010-10-14 Thread Martin v. Löwis
Am 14.10.2010 19:57, schrieb Daniel Stutzbach: > On Thu, Oct 14, 2010 at 12:38 PM, barry.warsaw > mailto:python-check...@python.org>> wrote: > > -# Generated by GNU Autoconf 2.65 for python 3.2. > +# Generated by GNU Autoconf 2.67 for python 3.2. > > > Was the change in autoconf versions

Re: [Python-Dev] [Python-checkins] r85486 - python/branches/py3k/configure

2010-10-14 Thread Daniel Stutzbach
On Thu, Oct 14, 2010 at 12:38 PM, barry.warsaw wrote: > -# Generated by GNU Autoconf 2.65 for python 3.2. > +# Generated by GNU Autoconf 2.67 for python 3.2. > Was the change in autoconf versions intentional and/or is it a problem? -- Daniel Stutzbach, Ph.D. President, Stutzbach Enterprises, LL