After looking at the web-page I found: """ Since their introduction, Unicode strings have supported an encode() method to convert the string to a selected encoding such as UTF-8 or=20 Latin-1. A symmetric decode([encoding]) method has been added to both 8-bit and Unicode strings in 2.2, which assumes=20 that the string is in the specified encoding and decodes it. This means that encode() and decode() can be called on=20 both types of strings, and can be used for tasks not directly related to Unicode. """ I did want to add unicode_string.decode(), but there was unexpected opposition to this small addition, so I decided to postpone the change. As a result, things are not as symmetric as they could be=20 in 2.2. I hope that Walter D=F6rwald finishes the codec callback=20 error handling patch before 2.2a2... it would make a great difference to the XML crowd. --=20 Marc-Andre Lemburg CEO eGenix.com Software GmbH ______________________________________________________________________ Consulting & Company: http://www.egenix.com/ Python Software: http://www.lemburg.com/python/
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