A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2006-January/059436.html below:

[Python-checkins] commit of r41907- python/trunk/Makefile.pre.in)

[Python-Dev] buildno (Was: [Python-checkins] commit of r41907- python/trunk/Makefile.pre.in)Armin Rigo arigo at tunes.org
Thu Jan 5 20:38:33 CET 2006
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.build_number should go, and be replaced with sys.svn_info,
> which should also include the branch from which the checkout/export
> was made. $Revision$ 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
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4