Hey, author here, thanks a lot Demian for even suggesting such a thing :). I'm really glad that people have found jsonschema useful. I actually tend these days to think similarly to what Nick mentioned, that the standard library really has decreased in importance as pip has shaped up and now been bundled -- so overall my personal opinion is that I wouldn't personally be pushing to get jsonschema in -- but! If you felt strongly, just some brief answers -- I think jsonschema would be able to cope with more restricted release cycles. And there are a few areas that I don't like about jsonschema (some APIs) which eventually I'd like to fix (RefResolver in particular), but for the most part I think it has stabilized more or less. I can provide some more details if there's any interest. Thanks again for even proposing such a thing :) -Julian On Thu, May 21, 2015 at 2:15 AM, wrote:

------------------------------

Message: 7 Date: Thu, 21 May 2015 19:15:20 +1000 From: Nick Coghlan To: Paul Moore Cc: Demian Brecht , Python-Ideas Subject: Re: [Python-ideas] Adding jsonschema to the standard library Message-ID: Content-Type: text/plain; charset=UTF-8

On 21 May 2015 at 17:57, Paul Moore wrote:

...

On 21 May 2015 at 06:29, Demian Brecht wrote:

...

Has been publicly available for over a year: v0.1 released Jan 1, 2012, currently at 2.4.0 (released Sept 22, 2014) Heavily used by the community: Currently sees ~585k downloads per month according to PyPI

One key question that should be addressed as part of any proposal for inclusion into the stdlib. Would switching to having feature releases only when a new major Python version is released (with bugfixes at minor releases) be acceptable to the project? From the figures you quote, it sounds like there has been some rapid development, although things seem to have slowed down now, so maybe things are stable enough.

The other question to be answered these days is the value bundling offers over "pip install jsonschema" (or a platform specific equivalent). While it's still possible to meet that condition, it's harder now that we offer pip as a standard feature, especially since getting added to the standard library almost universally makes life more difficult for module maintainers if they're not already core developers.

I'm not necessarily opposed to including JSON schema validation in general or jsonschema in particular (I've used it myself in the past and think it's a decent option if you want a bit more rigor in your data validation), but I'm also not sure how large an overlap there will be between "could benefit from using jsonschema", "has a spectacularly onerous package review process", and "can't already get jsonschema from an approved source".

Cheers, Nick.

-- Nick Coghlan | ncoghlan@gmail.com | Brisbane, Australia