Skip to content

PEP 744: JIT Compilation #3751

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
Merged
brandtbucher merged 14 commits into from
Apr 12, 2024
Merged

PEP 744: JIT Compilation #3751

brandtbucher merged 14 commits into from
Apr 12, 2024

Conversation

@brandtbucher
Copy link
Member

@brandtbucher brandtbucher commented Apr 11, 2024 •
edited by hugovk
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--3751.org.readthedocs.build/pep-0744/

@brandtbucher brandtbucher requested a review from a team as a code owner April 11, 2024 18:44
JelleZijlstra
JelleZijlstra reviewed Apr 11, 2024
View reviewed changes
Copy link
Member

@JelleZijlstra JelleZijlstra left a comment

Choose a reason for hiding this comment

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

Exciting! I noticed a few typos.

@hugovk hugovk added the new-pep A new draft PEP submitted for initial review label Apr 11, 2024
hugovk
hugovk reviewed Apr 11, 2024
View reviewed changes
hauntsaninja
hauntsaninja reviewed Apr 11, 2024
View reviewed changes
hugovk
hugovk approved these changes Apr 11, 2024
View reviewed changes
@brandtbucher
Copy link
Member Author

brandtbucher commented Apr 11, 2024

Alright, I think I've addressed everyone's comments. I'll leave this up for another hour or so.

@brandtbucher brandtbucher merged commit 0c92bbf into python:main Apr 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@hugovk hugovk hugovk approved these changes

@JelleZijlstra JelleZijlstra JelleZijlstra approved these changes

@hauntsaninja hauntsaninja hauntsaninja approved these changes

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.

4 participants

@brandtbucher @JelleZijlstra @hugovk @hauntsaninja