PEP 735: Add a canonical spec link

[sirosen]

Now that a specification document is in place on the packaging site, it is possible to update this PEP to link to it.

---

The PR templates don't seem to fit this case exactly, so I assume it's fine to make this change like so.

---

📚 Documentation preview 📚: https://pep-previews--4209.org.readthedocs.build/

[AA-Turner]

We generally add canonical links when marking PEPs as Final. Is there anything outstanding before doing so here?

A

[sirosen]

Ah, maybe I was mistaken about this being the time to do this. It's been on my to-do list, but I don't know if there are other steps to take before it's marked Final.

I'll reread the difference between Accepted and Final to make sure I understand.

[brettcannon]

I may have hit "merge" a bit too fast. 😅 But I also noticed that Paul didn't specify an acceptance criteria to transition to Final.

[sirosen]

I can do a fast-follow PR to mark it Final. I don't think there's anything left for a packaging PEP. Should I?

[AA-Turner]

PEP 1 says:

If changes based on implementation experience and user feedback are made to Standards track PEPs while in the Provisional or (with SC approval) Accepted state, they should be noted in the PEP, such that the PEP accurately describes the implementation at the point where it is marked Final.

So unless implementation of PEP 735 led to anything that should be updated in the text, it makes sense to open the PR to mark 735 as Final -- we can ask Paul to review that one to confirm. Thank you!

A