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/2005-December/058902.html below:

[Python-Dev] Expose Subversion revision number to Python

[Python-Dev] Expose Subversion revision number to Python [Python-Dev] Expose Subversion revision number to Python"Martin v. Löwis" martin at v.loewis.de
Mon Dec 19 23:22:10 CET 2005
John Pinner wrote:
> It's also the only thing that identifes the revision/build precisely,
> allowing reversion to a known state.

How so?
- It doesn't identify a build precisely: you may have dynamically-loaded
  modules that get rebuild even though the build number doesn't change.
  So a single build number may refer to different sets of code.
- it doesn't allow reversion to a known state: I can't even find a
  meaningful interpretation of such a claim. How would the build allow
  to revert anything? And what is that anything that it would allow to
  revert? Reverting doesn't work for source changes, nor for configure
  options (svn revert allows to do the former, in a limited way; svk
  allows that in a broader way).

Regards,
Martin
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