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

Reserve a PEP #683

Merged
merged 3 commits into from Jun 21, 2018
Merged

Reserve a PEP #683

merged 3 commits into from Jun 21, 2018

Conversation

@warsaw
Copy link
Member

@warsaw warsaw commented Jun 21, 2018

No description provided.

@warsaw warsaw self-assigned this Jun 21, 2018
@warsaw warsaw requested a review from Mariatta Jun 21, 2018
@Mariatta
Copy link
Member

@Mariatta Mariatta commented Jun 21, 2018

@warsaw I've started writing up my PEP which I want to be PEP 581: https://github.com/python/peps/pull/681/files

Can I just number it PEP 581 then?
My understanding is a PEP editor will assign the number for me.

@warsaw
Copy link
Member Author

@warsaw warsaw commented Jun 21, 2018

@Mariatta Yes, you can just take 581, no need for an editor to assign it to you. In general these days, folks with commit privileges just take the next available number. The PEP editors are there for "special cases" :). I can remove 581.rst from this PR if you like, or you can approve this, we can merge it now, and then your branch will just fill in the actual content. It's up to you!

@Mariatta
Copy link
Member

@Mariatta Mariatta commented Jun 21, 2018

Thanks @warsaw. I'll rename my PEP to PEP 581 :)

@warsaw warsaw merged commit a5ac5e1 into master Jun 21, 2018
2 checks passed
2 checks passed
continuous-integration/travis-ci/pr The Travis CI build passed
Details
continuous-integration/travis-ci/push The Travis CI build passed
Details
@warsaw warsaw deleted the reserved branch Jun 21, 2018
@warsaw warsaw changed the title Reserve two PEPs Reserve a PEP Jun 21, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

3 participants