[Python-Dev] buildno (Was: [Python-checkins] commit of r41907- python/trunk/Makefile.pre.in) (original) (raw)
Armin Rigo arigo at tunes.org
Thu Jan 5 20:38:33 CET 2006
- Previous message: [Python-Dev] buildno (Was: [Python-checkins] commit of r41907- python/trunk/Makefile.pre.in)
- Next message: [Python-Dev] bsddb broken
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi Martin,
On Thu, Jan 05, 2006 at 12:36:40AM +0100, "Martin v. L?wis" wrote:
OTOH, I also think we should get rid of buildno entirely. Instead, svnversion should be compiled into the object file, or, if it is absent, $Revision$ should be used; the release process should be updated to force a commit to the tag/Modules/buildno.c right after creating the tag. sys.buildnumber should go, and be replaced with sys.svninfo, which should also include the branch from which the checkout/export was made. RevisionRevisionRevision should only be trusted if it comes from a tag/.
All this sounds good.
Should I write a PEP for that?
I agree with Barry that it's overkill to ask for PEPs for too many small details.
A bientot,
Armin
- Previous message: [Python-Dev] buildno (Was: [Python-checkins] commit of r41907- python/trunk/Makefile.pre.in)
- Next message: [Python-Dev] bsddb broken
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]