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.

Sign up for GitHub

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

Jump to bottom

PEP 676: PEP Infrastructure Process #2173

Merged
merged 1 commit into from
Dec 2, 2021
Merged

PEP 676: PEP Infrastructure Process #2173

merged 1 commit into from
Dec 2, 2021

Conversation

AA-Turner
Copy link
Member

Submitting here to claim a PEP number as advised by Nick.

(I haven't added Mariatta to CODEOWNERS yet as I think a PEP number needs to be assigned first)

A

@AA-Turner AA-Turner requested a review from a team as a code owner December 2, 2021 12:39
@JelleZijlstra
Copy link
Member

You should be able to take PEP 676.

@AA-Turner AA-Turner force-pushed the peps-python-org-pep branch from 472dc4d to 2de3cc6 Compare December 2, 2021 14:58
@AA-Turner
Copy link
Member Author

@JelleZijlstra done

@AA-Turner AA-Turner changed the title PEP 9999: PEP Infrastructure Process PEP 676: PEP Infrastructure Process Dec 2, 2021
Mariatta
Mariatta approved these changes Dec 2, 2021
View reviewed changes
Copy link
Member

@Mariatta Mariatta left a comment

Choose a reason for hiding this comment

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

Looks great! Thanks for working on this!

@Mariatta
Copy link
Member

Mariatta commented Dec 2, 2021

I think this needs approval from @python/pep-editors. So I'll let them review and merge.

Once merged (and deployed), I believe the next step is to announce the PEP in python-dev mailing list (but point people to continue discussion on Discourse).

@brettcannon brettcannon merged commit 54e9bd0 into python:main Dec 2, 2021
@brettcannon
Copy link
Member

Approved and merged!

@Mariatta
Copy link
Member

Mariatta commented Dec 2, 2021

It's now live at https://www.python.org/dev/peps/pep-0676/

@AA-Turner
Copy link
Member Author

So should I submit this to the SC for an official decision at the same time as emailing python-dev, or afterwards?

A

@hugovk
Copy link
Member

hugovk commented Dec 3, 2021

It would also be good to get #2178 merged so that we can also see this PEP at https://python.github.io/peps/pep-0676/ :)

@AA-Turner AA-Turner deleted the peps-python-org-pep branch December 3, 2021 14:58
@Mariatta
Copy link
Member

Mariatta commented Dec 3, 2021

So should I submit this to the SC for an official decision at the same time as emailing python-dev, or afterwards?

Usually we'd announce the PEP to python-dev first, and gather feedback and concerns from the wider community. Once those have been addressed then you can submit the PEP to SC for decision.

@AA-Turner
Copy link
Member Author

OK, will do that then -- it would likely be towards christmas / late december as I am rather time constrained up to the 23rd, sorry.
A

@erlend-aasland erlend-aasland mentioned this pull request May 13, 2022
Closed
@erlend-aasland erlend-aasland mentioned this pull request Jun 27, 2022
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@Mariatta Mariatta Mariatta approved these changes

@brettcannon brettcannon brettcannon approved these changes

Assignees
No one assigned
Labels
CLA signed
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
6 participants
@AA-Turner @JelleZijlstra @Mariatta @brettcannon @hugovk @the-knights-who-say-ni