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 approachfor json as well. Once bytes-everywhere works, then a text API can bebuilt on top of it, but it is difficult to build a bytes API on top of atext 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
PGP.sig
Description: This is a digitally signed message part
_______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com