On Tue, 10 Aug 1999, Fredrik Lundh wrote: >... > unicode objects do not implement the getcharbuffer slot. This is Goodness. All righty. >... > maybe the unicode class shouldn't implement the > buffer interface at all? sure looks like the best way It is needed for fp.write(unicodeobj) ... It is also very handy for C functions to deal with Unicode strings. > to avoid trivial mistakes (the current behaviour of > fp.write(unicodeobj) is even more serious than the > marshal glitch...) What's wrong with fp.write(unicodeobj)? It should write the unicode value to the file. Are you suggesting that it will need to be done differently? Icky. > or maybe the buffer design needs an overhaul? Not that I know of. Cheers, -g -- Greg Stein, http://www.lyra.org/
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