ISTM, we can decide to limit 3.0's impact to a single compatibility module,
essentially as an alternate set of builtins.
import __new_builtins__
for name in 'bytes dict coerce'.split(): # list any new features you want
to support
setattr(__builtins__, name, getattr(__new_builtins__, name))
The bytes type would just be the new type.
The dict would have keys=iterkeys, no has_key, etc.
The coerce function would work but have a DeprecationWarning or somesuch.
If you want future division, we already have a mechanism for that.
If you want to eliminate backticks, just grep for them.
If you don't care about 3.0 compatibilty, just don't import the module.
Outside of a compatibility module, we can decide to leave Py2.6 unmolested by
Py3.0, so I can stop being cranky.
Raymond
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