PEP 739: specify how to handle conflicting installs

[FFY00]

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

---

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

[hugovk]

(I've added the checklist to the PR description.)

This is an accepted PEP, so needs SC approval:

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.

https://peps.python.org/pep-0001/#pep-maintenance

Please can you ask the SC about this change?