> How about an optional warning which, after a year or so, would be turned > on by default, and then a year or so after that would be an error? > > This same issue may effect some eventual merging of literal strings and > Unicode literals because \N, \u etc. are treated differently in strings > than in Unicode literals. And even if literal strings and Unicode > strings are never merged, \N could be useful in ordinary strings. -1 I don't find this enough of a problem to invoke the heavy gun of a language change. --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