> Why do you think that this would be that certainly possible? > I cannot imagine an efficient implementation. > > > Ah, but can you imagine an inefficient one? I think so (although one can never know until it's implemented). > If so, we're no longer > arguing about whether it's possible, but whether we want to pay the > price. Given that the dict.keys/values/items change hasn't been written > and only broadly designed, it's hard to tell *right now* what we can do > to ease the transition. I do believe we should be prepared to as much as > we can, in Python 2.6 and 2.7, to ease it (and the other transitions.) > That means the 2to3 tool and warnings in appropriate places, and > anything else we can do. I don't think we should do *everything* we can. If 2.6 performance will suffer significantly to support 3.x warnings, the price would be too high. Regards, Martin
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