Barry A. Warsaw [bwarsaw@cnri.reston.va.us] wrote: > All very cool things that could easily wait until 1.7. After all, > what's in a number? If, as Andrew puts forth, getting a stable Python > release with Unicode is very important for Python's future > positioning, then I say let's go with his more modest list, mainly > Unicode, sre, and Distutils. We've already got string meths, tons of > library improvements, and sundry other things. That's a good enough > laundry list for the next release. Heck, Python is infinately more conservative in its numbering than a lot of projects. All that was mentioned would normally be enough to call it 2.0 easily. :-) Modesty can be counter productive in PR business...also there is the issue of having two copies of 1.5.x installed at the same time, which with Unicode could be a manjor consideraton for some of us. For me, numbering has always been (and I try and keep it this way with Zope): X.Y.Z X = structural changes, backward incompaibility Y = new features Z = bug fixes only Chris -- | Christopher Petrilli | petrilli@amber.org
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