PEP 810: Explicit lazy imports

thomas · October 14, 2025, 7:32pm

FYI, the updated PEP was sent to the SC today:

PEP 810 – Explicit lazy imports

opened 03:26PM - 14 Oct 25 UTC

PEP

After a lot of discussion we'd like to submit PEP 810 (Explicit lazy imports) fo…r your consideration. https://peps.python.org/pep-0810/ Although the volume of the discussion has been quite challenging, we're genuinely humbled by the reception this has gotten. We are confident this addresses a real and pressing need in the community, as evidenced by the strong support from major library maintainers (too many to put here, check the discussion itself), the Scientific Python community, several major companies (including Meta, Google, Bloomberg, HRT and more) who've shared detailed feedback from their production deployments and many community members including educators and users working in academia. The discussion has been open since October 3rd and has gotten over 300 substantive comments. After several iterations incorporating feedback, we feel confident the discussion has converged and the PEP reflects the best proposal we can offer. We've documented the design space extensively with a large Rejected Ideas section explaining our rationale, a Deferred Ideas section for things that are out of scope but could be future work, and a comprehensive FAQ covering the questions that came up during discussion. We're available if you have specific questions or need clarification on anything. Thanks for your consideration! The PEP 810 authors ---- * [x] The PEP has been discussed in threads listed in its `Post-History` header * [x] The PEP was announced on [Discuss](https://discuss.python.org/t/pep-810-explicit-lazy-imports/104131/300) (link in `Post-History`) * [x] The PEP includes all relevant [Suggested Sections](https://peps.python.org/pep-0012/#suggested-sections) * [x] The PEP includes endorsements from the projects/groups/people it helps * [x] The PEP has a CODEOWNERS entry