Anthony Baxter wrote: > If it can be shown that this is a pure win (that is, it improves code > for 2.3.4, but is both backwards and forwards compatible, then I don't > mind. I _do_ mind if we end up with the horror of 2.2.2's not-really- > booleans, which has resulted in FAR FAR too much code of the form: > > try: > True, False > except: > True, False = 1, 0 It depends on the usage. If applications just do foo.encode("some-cjk-encoding") then all will work fine. However, it may be that applications do try: codecs.lookup("some-cjk-encoding") except LookupError: try: import japanese japanese.register_aliases() except ImportError: pass 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