"M.-A. Lemburg" wrote: > >... > > Since hexlify() uses a parser marker which does not involve a > type check, there's no way to have it reject Unicode objects. Well, we do have the option of changing the code! We could have hexlify check that its argument type is not Unicode or, more likely, remove the buffer interface from Unicode objects. I think that's the logical outcome of Guido's belief that Python programmers do NOT need access to the internal representation of string objects. The buffer interface seems to be only in existence to give access to internal representations of objects. Paul Prescod
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