@ncoghlan ah ok, I was not sure since many other entries in the specifications page are merely pointers to the related PEP.

At which point should we copy the spec here? I assume the PEP should move out of Draft state first?

@sbidoul We used to use the PEPs as the primary reference, so we've just been opportunistically migrating them as they get updated for other reasons (e.g. PEP 566 was really about defining metadata 2.1, but it also migrated to using packaging.python.org as the main reference page for the core metadata spec).

But yeah, for the initial draft, it makes sense to get it to Accepted before duplicating all the details over here. The key thing to add to the PEP is the long term URL you plan to use, and I think your suggestion of https://packaging.python.org/specifications/direct-url is a clear and sensible choice.

The key thing to add to the PEP is the long term URL you plan to use, and I think your suggestion of https://packaging.python.org/specifications/direct-url is a clear and sensible choice

@ncoghlan done in python/peps#1283

I updated this PR with the full specification extracted from PEP 610.

cc/ @ncoghlan @pradyunsg

@pradyunsg indeed, I only tweaked rst formatting (title underlines and roles), and adjusted the first few lines so it reads better.

This reminds me, though, that I had said that I'd leave out the part about resolved_revision and resolved_revision_type in the spec, because it is currently not implemented anywhere. So I've just added a commit removing that.