On 22 August 2015 at 05:27, Wes Turner <wes.tur...@gmail.com> wrote: > I guess what I'm trying to say is: > > * "why is this packaging metadata split?" > * shouldn't this all be in setup.py > > * couldn't we generate a proper RDF graph > from each of the latest JSONLD serializations > (e.g. https://pypi.python.org/pypi/<pkg>/jsonld)
We *could* do just about anything, but there's a reason I decided it was reasonable to put work on the overall metadata 2.0 spec on indefinite hiatus: given the difficult of getting folks to upgrade their build and deployment pipelines, we're currently still vastly better off finding smaller, more incremental steps that move the ecosystem forward, rather than engaging in a wholesale speculative redesign before we have any idea where folks would find the time to implement those changes not only in the core components (pip, PyPI, setuptools), but also throughout the wider ecosystem. As a result, at least until Warehouse is deployed to production, and we have TUF-based package signing available, it makes far more sense for us to pursue smaller tactical fixes that effectively address well-known problems with a minimum of development effort. Patience is one of the hardest development skills to learn (I regularly struggle with it myself), but when we don't apply ourselves to that task, not only do we significantly increase the likelihood of burning ourselves out, we're also likely to seriously annoy the folks around us. Personal prioritisation of effort is already difficult, and adding more people in a collaborative prioritisation process certainly doesn't make that any easier :) Regards, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
