R. David Murray <rdmur...@bitdance.com> added the comment: My understanding is that the reason that this particular version of autoconf is required is that newer versions introduce mixed line endings into the generated file, which causes problems with storing it in svn.
The introduction of the version check was prompted by the fact that several developers used the wrong autoconf version when regenerating the configure script because they weren't aware of this issue. In addition to this, however, having different developers regenerate the file using different autoconf versions would result in the checked-in configure script ping-ponging because of differing autoconf output. Thus it seems it is better in the general case to require that the configure script be built with a specified version of autoconf. ---------- nosy: +r.david.murray priority: -> normal resolution: -> invalid stage: -> committed/rejected status: open -> closed _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue6585> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
