Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly
Sign up
Appearance settings

PEP 739: Mark as Final #4629

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
FFY00 wants to merge 1 commit into python:main
base: main
Choose a base branch
Loading
from FFY00:pep739-final
Open

PEP 739: Mark as Final #4629

FFY00 wants to merge 1 commit into python:main from FFY00:pep739-final

Conversation

@FFY00
Copy link
Member

@FFY00 FFY00 commented Oct 4, 2025 •
edited by AA-Turner
Loading

  • 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 •
edited
Loading

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

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

Reviewers

@AA-Turner AA-Turner AA-Turner requested changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

AltStyle によって変換されたページ (->オリジナル) /