[Python-ideas] Adding jsonschema to the standard library

[Demian Brecht]

> On May 20, 2015, at 10:59 PM, Yury Selivanov <yselivanov.ml at gmail.com> wrote:
> I think we should wait at least until json-schema.org releases a final version of the spec.

I’d thought about that as well, but here were the arguments that I could think of that led me to proposing this in the first place:

The latest draft of the RFC expired Jan 31, 2013. I’d have to try to reach out to the author(s) to confirm, but I’d venture to say there likely isn’t much more effort being put into it.

The library is in heavy use and is useful in practice in its current state. I think that in situations like this practicality of a module should come first and finalized spec second.

There are numerous places in the library that deviate from specs in the name of practical use. I’m not advocating that shouldn’t be an exception as opposed to the rule, I’m just saying that there are multiple things to consider prior to simply squashing an inclusion because of RFC draft state.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 842 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://mail.python.org/pipermail/python-ideas/attachments/20150520/bca9e147/attachment.sig>