should be exported as part of the unicode object API. Otherwise, external C codec developers have to jump through some useless and silly hoops in order to construct a PyUnicode object. Additionally, you mentioned to Andrew that the decoders don't have to return a tuple anymore. Thats currently incorrect with whats currently in CVS: Python\codecs.c:PyCodec_Decode() current requires, but ignores the integer returned in the tuple. Should this be fixed, or must codecs return the integer as Misc\unicode.txt says? Thanks, Bill
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