Skip to content

Migrating interoperability specifications to PyPUG #11

Open
@ncoghlan

Description

@ncoghlan

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.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions