Martin v. Löwis wrote: >> This is what prompted my question, actually: in Py3k, in the >> str/unicode unification branch, r"\u1234" changes meaning: before the >> unification, this was an 8-bit string, where the \u was not special, >> but now it is a unicode string, where \u *is* special. >> > > That is true for non-raw strings also: the meaning of "\u1234" also > changes. > > However, traditionally, there was *no* escaping mechanism in raw strings > in Python, and I feel that this is a good principle, because it is > easy to learn (if you leave out the detail that \ can't be the last > character in a raw string - which should get fixed also, IMO). +1 Michael Foord
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