PEP 810: Explicit lazy imports

[pablogsal]

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--4622.org.readthedocs.build/pep-0810/

[AA-Turner]

Please add a CODEOWNERS entry, and fill in the new PEP template.

I'll work on an initial review of the content this evening.

A

[willingc]

I did a quick edit on the initial section before my flight was boarding. Will pick up the review in the next day or two.

[pablogsal]

I did a quick edit on the initial section before my flight was boarding. Will pick up the review in the next day or two.

Thanks a lot @willingc

[JelleZijlstra]

Very exciting to see this! Left some clarifying questions.

[AA-Turner]

Seconding other comments, an exciting and very thorough PEP! I've left various comments, let me know if more detail is needed for any of them.

Finally on further formatting banalities, please wrap the text of the PEP to 79 characters at some point before we merge this, per PEPs 1/12.

A

[Yhg1s]

Finally on further formatting banalities, please wrap the text of the PEP to 79 characters at some point before we merge this, per PEPs 1/12.

I've reflowed the entire thing (hopefully not breaking too much markup, but we'll see when the rebuild finishes.) I think some of your comments are proper discuss material or I'm not quite sure if I've addressed them adequately, so I've left them unresolved. Please resolve/remind as you see fit :)

[pablogsal]

I'm going to land the PEP because GitHub is crashing for me when addressing comments and suggestions. Additionally I want a final URL because some peeople are finding it confusing. PEP editors: please feel free to open a PR with your suggested changes (thanks a lot for them) if there are any of them missing or please feel free to comment here what we didn't address and we will make sure to update it.

Thanks for your understanding and thanks a lot for your excellent work ❤️

Comments addressed

[johnslavik]

I added a PR with support for highlighting lazy imports in the REPL and I'll be investigating some confusing errors in the REPL I found

[pablogsal]

I added a PR with support for highlighting lazy imports in the REPL and I'll be investigating some confusing errors in the REPL I found

Thanks so much for your enthusiasm and the PR! Just to set expectations: the reference implementation is primarily for evaluating the proposal itself and isn't meant to be a finished product at this stage. If the PEP gets accepted, we'd love your help with the final implementation: that's when we'll be building it out properly. Appreciate your interest in this!

[johnslavik]

I've reported a bunch of things that I found in the tracker. We can address them after the PEP is accepted. Thanks!