On Wed, Mar 17, 2010 at 1:44 PM, Raymond Hettinger <raymond.hettinger at gmail.com> wrote: > > On Mar 17, 2010, at 12:34 PM, Terry Reedy wrote: > > I agree. Improving 2.7 and not 3.2+ would give people a reason to not move > to 3.x. > > > FWIW, I think this is mischaracterizing the proposal. > The spectrum of options from worst to best is > 1) compare but give the wrong answer > 2) compare but give the right answer > 3) refuse to compare. > Py3.x is already in the best position, it refuses to compare. > IOW, is already is as improved as it can get. > P2.6 is in the worst position. The proposal is to make > it better, but not as good as 3.x. Some people have argued that (2) is better than (3). At the very least, there is a marked discontinuity in this spectrum between (2) and (3). With (1), users are less likely to rely on this feature in 2.x and then have no recourse when converting to 3.x. -- --Guido van Rossum (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