On 29 May 2002 at 15:52, Guido van Rossum wrote: > One question is how spin this. Listing a long > series of incompatibilities presents the image of a > language that has many gratuitous incompatible > changes -- which is not true and the opposite of > the message we want to convey. Hopefully, Python-in-a-tie changes the equilibrium somewhat. You can point the "pace of change" whiners to it (once there's something to point to <wink>); conversely, you needn't worry much about spinning a non-PyTie release. Because of the longer release cycle, a PyTie release *will* involve a lot of language changes. MAL's idea of a migration guide is great - just make sure it's presented as an "aid", not a "warning". -- Gordon http://www.mcmillan-inc.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