Oren Tirosh wrote:
> Yes, it might break some existing code that doesn't use proper \\ escaping
> or raw strings for regular expression. Note that such code is already
> broken in the sense that it uses an undefined escape.
"not proper"? "broken"? "undefined"?
Please read the section on string escapes in the *Python* language
reference, and try again. Start here:
http://www.python.org/doc/current/ref/strings.html
> If this turns out to be a real problem a possible alternative is to use
> curly braces. There is a precedent for this in u"\N{UNICODE CHAR NAMES}"
Last time I checked, the N in \N was a character, not a curly brace.
</F>
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