PEP 503 & PEP 691: Link to PyPA specifications

[woodruffw]

• Change is either:
  • To a Draft PEP
  • To an Accepted or Final PEP, with Steering Council approval
  • To fix an editorial issue (markup, typo, link, header, etc)
• PR title prefixed with PEP number (e.g. PEP 123: Summary of changes)

These PEPs have long since been canonicalized in the "Simple repository API" 🙂

---

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

[AA-Turner]

Just a note, it is helpful if you use the PR template, which reminds PR authors on title formatting. I'll add it to the description now.

A

[woodruffw]

Just a note, it is helpful if you use the PR template, which reminds PR authors on title formatting. I'll add it to the description now.

Oops, sorry about that. I'm actually not sure what happened there -- I clicked the "open a PR" link after doing git push but the PR body didn't populate like I think it normally does? Might have been PEBKAC.

[hugovk]

It's not you, it's a GitHub UI problem: they give the option when you visit the repo and open a PR via clicking the new PR button, but the git push link does not.