This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ncoghlan
Recipients barry, chrism, ncoghlan, pitrou, serhiy.storchaka
Date 2013-12-01.23:09:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CADiSq7cynVuOh5soq_-9cyFbt00bNfAQA3HG1qCC8t5mGJDB-g@mail.gmail.com>
In-reply-to <1385932890.2297.25.camel@fsol>
Content
The parallel API would have to be:

json.dump_bytes
json.dumps_bytes
json.load_bytes
json.loads_bytes

That is hardly an improvement over:

json.bytes.dump
json.bytes.dumps
json.bytes.load
json.bytes.loads

It doesn't need to be documented as a completely separate module, it can
just be a subsection in the json module docs with a reference to the
relevant RFC.

The confusion is inherent in the way the RFC was written, this is just an
expedient way to resolve that: the json module implements the standard, the
bytes submodule implements the RFC.

"Namespaces are a honking great idea; let's do more of those"
History
Date User Action Args
2013-12-01 23:09:55ncoghlansetrecipients: + ncoghlan, barry, chrism, pitrou, serhiy.storchaka
2013-12-01 23:09:55ncoghlanlinkissue19837 messages
2013-12-01 23:09:55ncoghlancreate