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 757: Set status to Accepted #4140

Merged
merged 1 commit into from
Nov 28, 2024
Merged

Conversation

vstinner
Copy link
Member

@vstinner vstinner commented Nov 28, 2024


📚 Documentation preview 📚: https://pep-previews--4140.org.readthedocs.build/

@vstinner vstinner merged commit 5074ef6 into python:main Nov 28, 2024
5 checks passed
@vstinner vstinner deleted the pep757_accepted branch November 28, 2024 15:28
@hugovk hugovk changed the title Set PEP 757 status to Accepted PEP 757: Set status to Accepted Nov 28, 2024
@@ -4,11 +4,12 @@ Author: Sergey B Kirpichev <[email protected]>,
Victor Stinner <[email protected]>
PEP-Delegate: C API Working Group
Copy link
Member

Choose a reason for hiding this comment

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

Has the SC confirmed the WG delegation for this PEP?

python/steering-council#259 says this PEP is special, and in general there is no standing delegation, but I don't see a clear decision regarding this PEP.

cc @Yhg1s

Copy link
Member Author

Choose a reason for hiding this comment

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

PEP 757 was created from capi-workgroup/decisions#35 : it's a working document for the C API Working Group to help to take a decision. I created PEP 757 with PEP-Delegate: C API Working Group.

Copy link
Member Author

Choose a reason for hiding this comment

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

There was a misunderstanding on my side about the C API WG ability to handle their own PEPs.

I submitted PEP 757 to the Steering Council.

Type: Standards Track
Created: 13-Sep-2024
Python-Version: 3.14
Post-History: `14-Sep-2024 <https://discuss.python.org/t/63895>`__
Resolution: https://discuss.python.org/t/pep-757-c-api-to-import-export-python-integers/63895/73
Copy link
Member

Choose a reason for hiding this comment

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

We can now include the date here too:

Suggested change
Resolution: https://discuss.python.org/t/pep-757-c-api-to-import-export-python-integers/63895/73
Resolution: `28-Nov-2024 <https://discuss.python.org/t/pep-757-c-api-to-import-export-python-integers/63895/73>`__

Copy link
Member Author

Choose a reason for hiding this comment

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

Oh, interesting, I will do the change when I will mark the PEP as Final.

vstinner added a commit to vstinner/peps that referenced this pull request Nov 28, 2024
vstinner added a commit that referenced this pull request Nov 28, 2024
gvanrossum pushed a commit to gvanrossum/peps that referenced this pull request Dec 10, 2024
gvanrossum pushed a commit to gvanrossum/peps that referenced this pull request Dec 10, 2024
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.

2 participants