On Wed, Jul 30, 2008 at 8:09 AM, André Malo <nd at perlig.de> wrote: > I'm actually in favour of encoding bytes only back and forth. A useful > extension would be *another* function which wraps quote/unquote and encodes > and decodes characters. I'd reverse this. By all means, add a new pair of functions that is bytes in / bytes out. But keep the existing functions purely string in / string out, hardcoded to UTF-8. People wanting another encoding can use the bytes functions and explicit encode / decode calls. -- --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