On 5/10/07, "Martin v. Löwis" <martin at v.loewis.de> wrote: > > However, I understand the other reason (inclusion of non-ASCII > > characters in raw strings) and I reluctantly agree with it. > > I actually disagree with that. It is fairly easy to include non-ASCII > characters in a raw Unicode string - just type them in. That violates the convention used in many places that source code should only contain printable ASCII, and all non-ASCII or unprintable characters should be written using \x or \u escapes. > Or, if that > fails, use string concatenation with a non-raw string: > > r"foo\uhallo" "\u20ac" r"welt" That makes for pretty unreadable source code though. Looking for a third opinion, -- --Guido van Rossum (home page: http://www.python.org/~guido/)
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