[Python-Dev] Bumping autoconf from 2.68 to 2.69 (original) (raw)

Charles-François Natali neologix at free.fr
Tue Oct 16 10:43:37 CEST 2012

My understanding is that we use a specific version of autoconf. The reason is that otherwise we end up with useless churn in the repo as the generated file changes when different committers use different versions. In the past we have had issues with a new autoconf version actually breaking the Python build, so we also need to test a new version before switching to it.

Well, so I guess all committers will have to use the same Linux/FreeBSD/whatever distribution then? AFAICT there's no requirement regarding the mercurial version used by committers either.

Charles

More information about the Python-Dev mailing list