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
signature.asc
Description: PGP signature
_______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
