Skip to content

PEP 818: Upstreaming the Pyodide JS FFI #4739

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
Open
hoodmane wants to merge 1 commit into
base: main
Choose a base branch
from
Open

PEP 818: Upstreaming the Pyodide JS FFI #4739

hoodmane wants to merge 1 commit into from
+3,299 −1

Conversation

@hoodmane
Copy link
Contributor

@hoodmane hoodmane commented Dec 10, 2025 •
edited
Loading

Basic requirements (all PEP Types)

  • Read and followed PEP 1 & PEP 12
  • File created from the latest PEP template
  • PEP has next available number, & set in filename (pep-NNNN.rst), PR title (PEP 123: <Title of PEP>) and PEP header
  • Title clearly, accurately and concisely describes the content in 79 characters or less
  • Core dev/PEP editor listed as Author or Sponsor, and formally confirmed their approval
  • Author, Status (Draft), Type and Created headers filled out correctly
  • PEP-Delegate, Topic, Requires and Replaces headers completed if appropriate
  • Required sections included
    • Abstract (first section)
    • Copyright (last section; exact wording from template required)
  • Code is well-formatted (PEP 7/PEP 8) and is in code blocks, with the right lexer names if non-Python
  • PEP builds with no warnings, pre-commit checks pass and content displays as intended in the rendered HTML
  • Authors/sponsor added to .github/CODEOWNERS for the PEP

Standards Track requirements

  • PEP topic discussed in a suitable venue with general agreement that a PEP is appropriate
  • Suggested sections included (unless not applicable)
    • Motivation
    • Rationale
    • Specification
    • Backwards Compatibility
    • Security Implications
    • How to Teach This
    • Reference Implementation
    • Rejected Ideas
    • Open Issues
  • Python-Version set to valid (pre-beta) future Python version, if relevant
  • Any project stated in the PEP as supporting/endorsing/benefiting from the PEP formally confirmed such
  • Right before or after initial merging, PEP discussion thread created and linked to in Discussions-To and Post-History

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

@hoodmane hoodmane requested a review from a team as a code owner December 10, 2025 21:31
@hoodmane hoodmane force-pushed the js-ffi branch 2 times, most recently from c55b8c8 to 7fe9188 Compare December 10, 2025 21:34
@hugovk
Copy link
Member

hugovk commented Dec 10, 2025

I've added the new PEP checklist (from https://github.com/python/peps/blob/main/.github/PULL_REQUEST_TEMPLATE/Add%20a%20new%20PEP.md), please could you check off as necessary?

@ambv Please can you confirm sponsorship?

@hoodmane hoodmane force-pushed the js-ffi branch 3 times, most recently from a6472ef to 82fbc12 Compare December 10, 2025 21:47
@hoodmane hoodmane changed the title PEP TBD: Upstreaming the Pyodide js ffi PEP 817: Upstreaming the Pyodide js ffi Dec 10, 2025
@hoodmane
Copy link
Contributor Author

hoodmane commented Dec 10, 2025

Thanks Hugo!

@hoodmane hoodmane force-pushed the js-ffi branch 2 times, most recently from 9c773b1 to abda220 Compare December 10, 2025 21:54
@hugovk hugovk mentioned this pull request Dec 10, 2025
Open
27 tasks
@hugovk hugovk changed the title PEP 817: Upstreaming the Pyodide js ffi PEP 9999: Upstreaming the Pyodide js ffi Dec 10, 2025
@hugovk
Copy link
Member

hugovk commented Dec 10, 2025

Let's renumber this to 9999 for now, we also have #4740 clashing.

@hoodmane hoodmane added the new-pep A new draft PEP submitted for initial review label Dec 10, 2025
@ambv
Copy link
Contributor

ambv commented Dec 11, 2025

@ambv Please can you confirm sponsorship?

Confirmed!

@hugovk
Copy link
Member

hugovk commented Dec 11, 2025

Thanks!

@hoodmane Please use PEP 818.

@hugovk hugovk changed the title PEP 9999: Upstreaming the Pyodide js ffi PEP 818: Upstreaming the Pyodide js ffi Dec 11, 2025
@hoodmane hoodmane force-pushed the js-ffi branch 2 times, most recently from 68edc4b to ec236c4 Compare December 11, 2025 16:57
@hoodmane
Copy link
Contributor Author

hoodmane commented Dec 11, 2025 •
edited by ambv
Loading

Okay updated it to say pep 818 everywhere.

@AA-Turner AA-Turner changed the title PEP 818: Upstreaming the Pyodide js ffi PEP 818: Upstreaming the Pyodide JS FFI Dec 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

new-pep A new draft PEP submitted for initial review

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@hoodmane @hugovk @ambv