On Apr 9, 2009, at 11:21 PM, Nick Coghlan wrote: > Barry Warsaw wrote: >> I don't know whether the parameter thing will work or not, but you're >> probably right that we need to get the bytes-everywhere API first. > > Given that json is a wire protocol, that sounds like the right > approach > for json as well. Once bytes-everywhere works, then a text API can be > built on top of it, but it is difficult to build a bytes API on top > of a > text one. Agreed! > So I guess the IO library *is* the right model: bytes at the bottom of > the stack, with text as a wrapper around it (mediated by codecs). Yes, that's a very interesting (and proven?) model. I don't quite see how we could apply that email and json, but it seems like there's a good idea there. ;) -Barry -------------- next part -------------- A non-text attachment was scrubbed... Name: PGP.sig Type: application/pgp-signature Size: 304 bytes Desc: This is a digitally signed message part URL: <http://mail.python.org/pipermail/python-dev/attachments/20090409/c1447da2/attachment.pgp>
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