-On [20080105 22:44], Jameson Chema Quinn ([EMAIL PROTECTED]) wrote:
>The "syntax" of what goes inside these is very loose.
>identifier_list ::= [<initial_word>]<opening_symbol> <content_word>
>{<separator_symbol> <content_word>} <closing symbol>
>, with no whitespace after initial_word, and where separator_symbol is the set
>of symbols ".,<>{}[]+-*^%=|/()[]{}" MINUS closing_symbol. content_word could
>maybe be a quoted string, too.
>In the "function name", no whitespace
>is allowed, but the symbols ".,*^=><-" are. Thus::Given the fact Python 3k will use unicode natively for strings and, IIRC, UTF-8 as standard encoding for Python files, have you thought about the half-width and full-width characters like the ones you describe above? 「」 are, for example, very common in Japanese where English would use quotes. -- Jeroen Ruigrok van der Werven <asmodai(-at-)in-nomine.org> / asmodai イェルーン ラウフロック ヴァン デル ウェルヴェン http://www.in-nomine.org/ | http://www.rangaku.org/ Possession is nine points of the law... _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
