Skip to content

Conversation

FFY00
Copy link
Member

@FFY00 FFY00 commented Oct 4, 2025

  • Final implementation has been merged (including tests and docs)
  • PEP matches the final implementation
  • Any substantial changes since the accepted version approved by the SC/PEP delegate
  • Pull request title in appropriate format (PEP 123: Mark as Final)
  • Status changed to Final (and Python-Version is correct)
  • Canonical docs/spec linked with a canonical-doc directive
    (or canonical-pypa-spec for packaging PEPs,
    or canonical-typing-spec for typing PEPs)

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

Signed-off-by: Filipe Laíns <lains@riseup.net>
@FFY00 FFY00 requested a review from a team as a code owner October 4, 2025 14:16
@AA-Turner AA-Turner changed the title PEP 739: mark as Final PEP 739: Mark as Final Oct 4, 2025
Copy link
Member

@AA-Turner AA-Turner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this be marked as Final whilst a Tier 1 platform is not yet supported (i.e. the final implementation has not yet been fully merged)? The PEP requires that:

Starting from Python 3.14, a file named build-details.json following the format specified in this PEP, or a future version, MUST be installed in the platform-independent standard library directory (stdlib, eg. /usr/lib/python3.14/build-details.json), UNLESS unfeasible due to technical limitations.

A

@FFY00
Copy link
Member Author

FFY00 commented Oct 4, 2025

Ah, right! Let's just wait a bit on the PR though 😊

@hugovk hugovk mentioned this pull request Oct 6, 2025
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants