[Python-3000] Support for PEP 3131 (original) (raw)
Steve Howell showell30 at yahoo.com
Fri May 25 14:49:12 CEST 2007
- Previous message: [Python-3000] Support for PEP 3131
- Next message: [Python-3000] Support for PEP 3131
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
--- "Stephen J. Turnbull" <stephen at xemacs.org> wrote:
Steve Howell writes:
> respect to Kanji, and switches over to Python, and > changes his little wrapper shell script to say "python > -U" instead of "ruby -Kkcode"? He could then start to > use non-Japanese Python modules while still writing > his own Python code in Japanese. But that's not enough. The problem is that the reason for -Kkcode is that kcode != Unicode. Japanese use several mutually incompatible encodings, and they mix anarchically over the Internet. What -K does is allow you to specify which one you're giving to the interpreter at runtime. The analogy to -K would be if you get a English-language Python source file from somewhere, look into it, realize it's from IBM, and run it with "python -K ebcdic whizbang.py". Same characters, only the bytes are changed to confuse the innocent. That's what -Kkcode is for.
I think you misintrepeted my post a bit. I wasn't suggesting that Python implement a flag that was exactly equivalent to the -K flag in Ruby. I understand the arguments that such a flag might be either unnecessary in Python, or unsatisfactory.
What I was trying to say here is that there might be precedent for non-ascii users already tolerating command line arguments.
____________________________________________________________________________________Luggage? GPS? Comic books? Check out fitting gifts for grads at Yahoo! Search http://search.yahoo.com/search?fr=oni_on_mail&p=graduation+gifts&cs=bz
- Previous message: [Python-3000] Support for PEP 3131
- Next message: [Python-3000] Support for PEP 3131
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]