Message 154014 - Python tracker

➜

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.

In-reply-to
Author	vinay.sajip
Recipients	loewis, vinay.sajip
Date	2012年02月22日.23:37:05
SpamBayes Score	4.057e-05
Marked as misclassified	No
Message-id	<1329953826.97.0.233883201006.issue14093@psf.upfronthosting.co.za>

Content
Currently, the Mercurial revision information is not appearing in Windows builds - they always appear to be "default". This appears to be because the relevant information is not passed to getbuildinfo.c. The attached patch rectifies this, making the assumption that "hg" will always be accessible on the path. The basic method is to call "hg id -bit" and then pass the branch, tag and revision information when compiling getbuildinfo.c. If "hg" is not in the path, no Mercurial information is added (i.e. the current behaviour).

Content

Currently, the Mercurial revision information is not appearing in Windows builds - they always appear to be "default". This appears to be because the relevant information is not passed to getbuildinfo.c.
The attached patch rectifies this, making the assumption that "hg" will always be accessible on the path. The basic method is to call "hg id -bit" and then pass the branch, tag and revision information when compiling getbuildinfo.c.
If "hg" is not in the path, no Mercurial information is added (i.e. the current behaviour).

History
Date	User	Action	Args
2012年02月22日 23:37:07	vinay.sajip	set	recipients: + vinay.sajip, loewis
2012年02月22日 23:37:06	vinay.sajip	set	messageid: <1329953826.97.0.233883201006.issue14093@psf.upfronthosting.co.za>
2012年02月22日 23:37:06	vinay.sajip	link	issue14093 messages
2012年02月22日 23:37:06	vinay.sajip	create

homepage