[Fred]
> Munge the RCS keywords to avoid updates, so the version number matches that
> of the PyUNIT version of the same file. This helps people understand that
> this version is the same as the version from the independent PyUNIT
> release (confusion was indicated on the PyUNIT mailing list).
But now it's gonna confuse Python developers. And what if Python's
unittest.py gets a life of its own? What is the meaning of the
version number then? I propose to remove the __author__, __email__
and __version__ strings, and instead include that information in the
docstring or in a comment.
> ! __version__ = "#Revision: 1.43 $"[11:-2]
Why not simply
__version__ = "1.43"
???
--Guido van Rossum (home page: http://www.python.org/~guido/)
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