SUZUKI Hisao <suzuki611@oki.com> writes: > And almost every operating system in Japan is on the way to > adopt Unicode to save us from the chaos. I am afraid the > mileage of the PEP will be fairly short and just results in > loading a lot of burden onto the language, That is a mis-perception. The PEP does not add a lot of burden onto the language; the stage-1 implementation is fairly trivial. The biggest change in the interpreter will be to have the parser operate on Unicode all the time; that change will be necessary stage 2, whether UTF-8 will be the default encoding or not. Also, the warning framework added will help people migrating - whether towards UTF-8 or custom locally-declared encodings is their choice. > I know it is not the best practice either. However, you cannot > safely write Shift_JIS into Python source file anyway, unless > you hack up the interpreter parser itself for now. In stage 2 of the PEP, this will be possible (assuming Python has access to a Shift_JIS 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