Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Hopefully they learned lessons from why PEP-690 was rejected. I've spent quite a while trying to build this stuff for our codebase and it's never worked well enough to use.




690 is mentioned a few times, including a FAQ note on the differences

https://pep-previews--4622.org.readthedocs.build/pep-0810/#f...

Q: How does this differ from the rejected PEP 690?

A: PEP 810 takes an explicit, opt-in approach instead of PEP 690’s implicit global approach. The key differences are:

Explicit syntax: lazy import foo clearly marks which imports are lazy.

Local scope: Laziness only affects the specific import statement, not cascading to dependencies.

Simpler implementation: Uses proxy objects instead of modifying core dictionary behavior.




Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: