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 Graeme.Winter, benjamin.peterson, georg.brandl, r.david.murray
Date 2011-06-16.14:22:56
SpamBayes Score 1.8702275e-06
Marked as misclassified No
Message-id <1308234177.47.0.709568039542.issue12346@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2011-06-16 14:22:57r.david.murraysetrecipients: + r.david.murray, georg.brandl, benjamin.peterson, Graeme.Winter
2011-06-16 14:22:57r.david.murraysetmessageid: <1308234177.47.0.709568039542.issue12346@psf.upfronthosting.co.za>
2011-06-16 14:22:56r.david.murraylinkissue12346 messages
2011-06-16 14:22:56r.david.murraycreate