PEP 805: Safe Parallel Python

[markshannon]

Basic requirements (all PEP Types)

• Read and followed PEP 1 & PEP 12
• File created from the latest PEP template
• PEP has next available number, & set in filename (pep-NNNN.rst), PR title (PEP 123: <Title of PEP>) and PEP header
  • Tip: find the next available number with pepotron — run uvx pepotron next (or pipx install pepotron then pep next)
• Title clearly, accurately and concisely describes the content in 79 characters or less
• Core dev/PEP editor listed as Author or Sponsor, and formally confirmed their approval
• Author, Status (Draft), Type and Created headers filled out correctly
• PEP-Delegate, Topic, Requires and Replaces headers completed if appropriate
• Required sections included
  • Abstract (first section)
  • Copyright (last section; exact wording from template required)
• Code is well-formatted (PEP 7/PEP 8) and is in code blocks, with the right lexer names if non-Python
• PEP builds with no warnings, pre-commit checks pass and content displays as intended in the rendered HTML
• Authors/sponsor added to .github/CODEOWNERS for the PEP

Standards Track requirements

• PEP topic discussed in a suitable venue with general agreement that a PEP is appropriate
• Suggested sections included (unless not applicable)
  • Motivation
  • Specification
  • Rationale
  • Backwards Compatibility
  • Security Implications
  • How to Teach This
  • Reference Implementation
  • Rejected Ideas
  • Open Issues
  • Acknowledgements
  • Footnotes
  • Change History
• Python-Version set to valid (pre-beta) future Python version, if relevant
• Any project stated in the PEP as supporting/endorsing/benefiting from the PEP formally confirmed such
• Right before or after initial merging, PEP discussion thread created and linked to in Discussions-To and Post-History

[markshannon]

I don't understand this message:

/home/runner/work/peps/peps/peps/pep-0554.rst:1832: WARNING: duplicate label c-api, other instance in /home/runner/work/peps/peps/peps/pep-0805.rst

Why is it a problem if PEP 554 and PEP 805 use the same label? They aren't connected.
PEP 805 does reference PEP 554. I'll try using a different label.

[read-the-docs-community]

Documentation build overview

📚 pep-previews | 🛠️ Build #34174797 | 📁 Comparing 37bc222 against latest (58c5ad3)

  🔍 Preview build  

34 files changed · + 3 added · ± 27 modified · - 4 deleted

+ Added

• pep-0805/index.html
• pep-0805/appendix-examples/index.html
• pep-0805/appendix-implementation/index.html

± Modified

• index.html
• numerical/index.html
• pep-0000/index.html
• pep-0001/index.html
• pep-0345/index.html
• pep-0444/index.html
• pep-0545/index.html
• pep-0694/index.html
• pep-0719/index.html
• pep-0727/index.html
• and 17 more...

- Deleted

• pep-0839/index.html
• pep-0841/index.html
• pep-0842/index.html
• pep-0844/index.html

[hugovk]

I don't understand this message:

/home/runner/work/peps/peps/peps/pep-0554.rst:1832: WARNING: duplicate label c-api, other instance in /home/runner/work/peps/peps/peps/pep-0805.rst

Why is it a problem if PEP 554 and PEP 805 use the same label? They aren't connected. PEP 805 does reference PEP 554. I'll try using a different label.

Explicit labels are global across the whole PEPs build, so :ref:s can point to a label in any other document in the build and not just within a single file.

So using a unique label is the correct fix.

[hugovk]

I don't understand this message:

/home/runner/work/peps/peps/peps/pep-0554.rst:1832: WARNING: duplicate label c-api, other instance in /home/runner/work/peps/peps/peps/pep-0805.rst

Why is it a problem if PEP 554 and PEP 805 use the same label? They aren't connected. PEP 805 does reference PEP 554. I'll try using a different label.

Explicit labels are global across the whole PEPs build, so :ref:s can point to a label in any other document in the build and not just within a single file.

So using a unique label is the correct fix.