> Python being 8-bit clean, it is less a problem with it than with languages > much relying on NUL terminated C strings. I hope that Python will stick > to its current UTF-8 behaviour, even if C extension writers were applying > some pressure for a change. Python won't change its story here. (We *will* get to the bottom of Barry's bug, which had nothing to do with this issue.) --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