[Python-Dev] [Python-checkins] r85486 - python/branches/py3k/configure (original) (raw)
Barry Warsaw barry at python.org
Thu Oct 14 20:53:59 CEST 2010
- Previous message: [Python-Dev] [Python-checkins] r85486 - python/branches/py3k/configure
- Next message: [Python-Dev] [Python-checkins] r85486 - python/branches/py3k/configure
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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 changing autoconf versions, the actual configure script will change forth and back, confusing attributions (svn blame).
While it's true that we use AC_PREREQ(2.65), that specifies only the minimum version of autoconf required. Any time configure.in changes, configure has to change too, and since it's a generated file, I think svn blame on configure is kind of useless.
Should we appoint an autoconf BDFL who can commit changes after configure.in is changed? Is it possible to pin the autoconf version (not just floor it)?
-Barry -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: not available URL: <http://mail.python.org/pipermail/python-dev/attachments/20101014/3dcb4c57/attachment.pgp>
- Previous message: [Python-Dev] [Python-checkins] r85486 - python/branches/py3k/configure
- Next message: [Python-Dev] [Python-checkins] r85486 - python/branches/py3k/configure
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]