The numbering scheme should cover this need. After all, Wirth
had a series of numbered versions for Modula (<empty>, 2, 3).
I think the individual modules may need explicit version
numbering, also. I find 15 of 158 .py files in my release of
the library have __version__ numbers.
I have a patch I use for the current release of the SGML module;
it may never make it to prime time (since it works around an
obscure MS-Word-ism). I may have to update it for future
releases, and would like to know which releases of the module
use wich version of the patch.
--- Peter Funk <pf@artcom-gmbh.de> wrote:
> Aahz to Skip:
> > > So don't keep proposing changes that break 1.5.2
> compatibility.
>
> Guido van Rossum:
> > -1. That means we could never deprecate a feature.
>
> Than don't do it! Simply never remove features from
> the language (whether the feature is documented or not).
>
> Do it like Niklaus Wirth: Always start with a fresh new name
> for the
> language, ...
=====
--
S. Lott, CCP :-{)
S_LOTT@YAHOO.COM
http://www.mindspring.com/~slott1
Buccaneer #468: KaDiMa
Macintosh user: drinking upstream from the herd.
__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com
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