PEP 621: Update requires-python link to intended core-metadata section

[brandonlenz]

Closes: #5033

• 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)

[python-cla-bot]

All commit authors signed the Contributor License Agreement.

[read-the-docs-community]

Documentation build overview

📚 pep-previews | 🛠️ Build #33563710 | 📁 Comparing 0e7f1f3 against latest (339af2b)

  🔍 Preview build  

2 files changed

± pep-0621/index.html
± pep-0764/index.html

[brettcannon]

@brandonlenz FYI, PEPs are historical documents once accepted, and as such are not typically kept in sync with anything. This PR was simple enough to accept (and thanks for taking the time!), but had it required any work to verify it would have been rejected.

[brandonlenz]

@brandonlenz FYI, PEPs are historical documents once accepted, and as such are not typically kept in sync with anything. This PR was simple enough to accept (and thanks for taking the time!), but had it required any work to verify it would have been rejected.

Totally understood! Thanks for taking the time to review 😄