[issue12346] Python 2.7.2 source code build (release) depends on mercurial

[R. David Murray]

R. David Murray <rdmurray at bitdance.com> added the comment:

It used to be that the svn version info was pulled from embedded constants in Makefile.pre.in.  I agree that depending on having mercurial (and, presumably, a repo!) at build time is wrong.  These constants need to be pre-computed when a release tarball is built and the mercurial dependency removed from the generated Makefile.  I'm not sure how we make that work correctly in a development build, but I'm sure the release managers will figure something out.

----------
nosy: +benjamin.peterson, georg.brandl, r.david.murray
priority: normal -> release blocker
stage:  -> needs patch
versions: +Python 3.2, Python 3.3

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue12346>
_______________________________________