[Jeremy] > Let me put my Python/Zope user hat on for a moment. I help maintain a > Zope cluster that runs Python 2.1. We're not going to have another > Zope release that uses Python 2.2 any time soon. When we do, it will > probably be Zope 3 and that will be hard for me to upgrade to. So I > expect the most recent Python I'll be using for the next year will be > Python 2.1. I'd really be grateful for bug fixes and maintenance on > this version as a result. Fair enough. > Put in a slightly more abstract way, Python 2.2 is a major release > with lots of new features. I expect a lot of users will stick with > the last minor release that isn't a major release in disguise :-). So > we'd serve them well be doing more maintenance on 2.1. Agreed -- with the caveat that we have fixed resources. > Also, I haven't yet found any response to /F's suggestion that the std > library always code to an earlier version of Python. What do you > think of that? I don't like it. --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