This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author r.david.murray
Recipients alexandre.vassalotti, cavallo71, pitrou, r.david.murray
Date 2009-07-27.22:20:08
SpamBayes Score 7.462364e-13
Marked as misclassified No
Message-id <1248733210.64.0.263984504453.issue6585@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2009-07-27 22:20:10r.david.murraysetrecipients: + r.david.murray, pitrou, alexandre.vassalotti, cavallo71
2009-07-27 22:20:10r.david.murraysetmessageid: <1248733210.64.0.263984504453.issue6585@psf.upfronthosting.co.za>
2009-07-27 22:20:08r.david.murraylinkissue6585 messages
2009-07-27 22:20:08r.david.murraycreate