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 741 -- Python Configuration C API #237

Closed
5 of 7 tasks
vstinner opened this issue Mar 14, 2024 · 5 comments
Closed
5 of 7 tasks

PEP 741 -- Python Configuration C API #237

vstinner opened this issue Mar 14, 2024 · 5 comments
Labels
PEP Python Enhancement Proposal

Comments

@vstinner
Copy link
Member

Please consider PEP 741 -- Python Configuration C API
https://peps.python.org/pep-0741/

  • The PEP has been discussed in threads listed in its Post-History header
  • The PEP was announced on Discuss (link in Post-History)
  • The PEP includes all relevant Suggested Sections
  • The PEP includes endorsements from the projects/groups/people it helps
  • The PEP has a CODEOWNERS entry

SIG-specific:

  • Typing PEPs: link to the Typing Council's recommendation for the PEP:
  • Packaging PEPs: don't file the issue here, ask the delegate (Paul Moore) on Packaging Discourse
@vstinner vstinner added the PEP Python Enhancement Proposal label Mar 14, 2024
@gvanrossum
Copy link
Member

Whoa. I do not think there is sufficient agreement on this in the discussion.

@zooba
Copy link
Member

zooba commented Mar 14, 2024

I agree. I have opposed the fundamental premise of this PEP in the discussion, and it's not been addressed in the discussion or changed at all.

I do not believe the SC should be considering this PEP at this time.

@vstinner
Copy link
Member Author

Whoa. I do not think there is sufficient agreement on this in the discussion.

I did my best to record all opinions in the Rejected Ideas. The PEP is already quite long, so I didn't record everything.

Right, there are disagreements, and that's why I'm asking the Steering Council for advice on how to move on on this PEP.

@vstinner
Copy link
Member Author

If this PEP is accepted, I plan to attempt to write a backport for Python 3.8-3.12 in my experimental deadparrot project: shared library providing a compatibility layer between old/new C APIs and old/new Python versions.

@vstinner
Copy link
Member Author

vstinner commented Jun 3, 2024

Closed in favor of the new submission: #246.

@vstinner vstinner closed this as completed Jun 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
PEP Python Enhancement Proposal
Projects
None yet
Development

No branches or pull requests

3 participants