Skip to content
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

PEP 670: Set Status to Final #2647

Merged
merged 1 commit into from
Jun 13, 2022
Merged

PEP 670: Set Status to Final #2647

merged 1 commit into from
Jun 13, 2022

Conversation

vstinner
Copy link
Member

No description provided.

@vstinner
Copy link
Member Author

While there is still activity on python/cpython#89653, IMO the main part of the PEP is implemented and so the PEP status can be set to Final. I propose to still push changes related to PEP 670 even after the PEP is marked as Final.

cc @erlend-aasland

@erlend-aasland
Copy link
Contributor

IMO the main part of the PEP is implemented and so the PEP status can be set to Final. I propose to still push changes related to PEP 670 even after the PEP is marked as Final.

I have no prior experience regarding when to mark PEP's as final, so I trust your judgement here :)

@AA-Turner
Copy link
Member

From PEP-1:

Once a PEP has been accepted, the reference implementation must be completed. When the reference implementation is complete and incorporated into the main source code repository, the status will be changed to “Final”.

A

@vstinner vstinner merged commit 41e1468 into python:main Jun 13, 2022
@vstinner vstinner deleted the pep670_final branch June 13, 2022 14:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants