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 676: Mark as accepted #2384

Merged
merged 1 commit into from
Mar 7, 2022
Merged

PEP 676: Mark as accepted #2384

merged 1 commit into from
Mar 7, 2022

Conversation

hugovk
Copy link
Member

@hugovk hugovk commented Mar 7, 2022

PEP-Delegate @warsaw accepted PEP 676 in https://discuss.python.org/t/10774/99 🎉

Copy link
Member

@JelleZijlstra JelleZijlstra left a comment

Choose a reason for hiding this comment

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

congratulations everyone!

@AA-Turner AA-Turner merged commit 8423526 into python:main Mar 7, 2022
@AA-Turner
Copy link
Member

We'll need a further update to Active when the implementation work is done (I've started discussion with the infrastructure team, so expect updates soon!)

A

@CAM-Gerlach
Copy link
Member

@AA-Turner FYI, the current classification logic sorts this PEP, along with e.g. PEP 581 (PEP-0581, the ongoing GitHub issues migration, which I noticed the other day) into the "Historical" category in PEP 0. I opened #2385 which fixes this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants