Re: Dropping bytes "support" in json
Barry Warsaw <[email protected]>
| Newsgroups | gmane.comp.python.devel,gmane.comp.python.mime.devel |
|---|---|
| Message-ID | <[email protected]> |
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 _______________________________________________ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/python-python-dev%40m.gmane.org
PGP.sig
(application/pgp-signature, 304 B) - not displayed