Message159366
Things are a little more complicated. '123' is not a valid JSON according to RFC 4627 (the top-level element can only be an object or an array). This means that the autodetection algorithm will not always work for such non-standard data.
If we can parse binary data, then there must be a way to generate binary data in at least one of the Unicode encodings.
By the way, the documentation should give a link to RFC 4627 and explain the current implementation is different from it. |
|
Date |
User |
Action |
Args |
2012-04-26 14:07:46 | serhiy.storchaka | set | recipients:
+ serhiy.storchaka, barry, georg.brandl, hhas, pitrou, ezio.melotti, eric.araujo, r.david.murray, docs@python, antlong, Balthazar.Rouberol |
2012-04-26 14:07:46 | serhiy.storchaka | set | messageid: <1335449266.36.0.187593044345.issue10976@psf.upfronthosting.co.za> |
2012-04-26 14:07:45 | serhiy.storchaka | link | issue10976 messages |
2012-04-26 14:07:45 | serhiy.storchaka | create | |
|