Hye-Shik Chang wrote: >>try: >> codecs.lookup("some-cjk-encoding") >>except LookupError: >> try: >> import japanese >> japanese.register_aliases() >> except ImportError: >> pass > > > This usage is useful only for -S mode. The recent Asian codecs > register its aliases by their respective .pth. So, backporting > CJK codecs won't let Japanese developers code in this way. Of course, users may have installed JapaneseCodecs with --without-aliases, in which case the aliases won't be there (neither automatically, nor after explicitly importing japanese). I believe mailman use it that way So people who currently do encodings.aliases.aliases.update( {"shift_jis" : "japanese.shift_jis"}) would have to adjust their code. I also find that installing JapaneseCodecs on top of a CJK-enabled Python 2.4 causes shift_jis to use the CJK codec, not the japanese codec. 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