[Python-ideas] Adding jsonschema to the standard library

[Nick Coghlan]

On 23 May 2015 at 12:59, Stephen J. Turnbull <stephen at xemacs.org> wrote:
> Donald Stufft writes:
>  > It's being solved for very specific cases by starting to have the
>  > standard documentation explicitly call out these defacto standards
>  > of the Python ecosystem where it makes sense.
>
> Because that's necessarily centralized, it's a solution to a different
> problem.  We need a decentralized approach to deal with the "people
> who use package X often would benefit from Y too, but don't know where
> to find Y or which implementation to use."  IOW, there needs to be a
> way for X to recommend implementation Z (or implementations Z1 or Z2)
> of Y.

https://www.djangopackages.com/ covers this well for the Django
ecosystem (I actually consider it to be one of Django's killer
features, and I'm pretty sure I'm not alone in that - like
ReadTheDocs, it was a product of DjangoDash 2010).

There was an effort a few years back to set up an instance of that for
PyPI in general, as well as similar comparison sites for Pyramid and
Plone, but none of them ever hit the same kind of critical mass of
useful input as the Django one.

The situation has changed substantially since then, though, as we've
been more actively promoting pip, PyPI and third party libraries as
part of the recommended Python developer experience, and the main
standard library documentation now delegates to packaging.python.org
for the details after very brief introductions to installing and
publishing packages.

Cheers,
Nick.

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