Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Migrating interoperability specifications to PyPUG #11
I have some time at the moment to work on upstream process improvement, and one of the things I'd like to tidy up is the change management process for interoperability specifications. Some relevant previous discussions:
Since that last discussion, @dstufft, @nlhkabu and @ddbeck have done a lot more design work on Warehouse and the user guide, so I've now come around to the view that the PyPA internal docs are likely to be a better home.
Rather than using PEP 440 or PEP 508 as guinea pigs, I'm thinking a better starting point might be PEP 376 (the database of installed Python distributions), since we can tweak the description on pypa.io to specifically cover the interoperability spec parts that pip implements, and omit the standard library API parts.
I'll put together a pull request along those lines, adding a new "PyPA Specifications" section, with process details (based on the first email linked above), and a section on the RECORD file and the directory naming scheme.
Not quite. What I'd like to do is shift to a model closer to the way
That way, if you just want the current spec, that's always readily
distutils-sig thread: https://mail.python.org/pipermail/distutils-sig/2016-January/028060.html
After reflecting on the PR and likely future workflows, I've switched to favouring a split approach where we put the process definition here (since it's really only relevant to PyPA & distutils-sig members), but have the specifications themselves on packaging.python.org.
The main purposes of that is to keep the packaging specifications on the same standing as the Language Reference and Library Reference in terms of "brand recognition" for their top level domain.
changed the title from
Migrating interoperability specifications to pypa.io
Migrating interoperability specifications to PyPUG
Jan 25, 2016