#pep810 — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #pep810, aggregated by home.social.
-
Black 26.5.0 is out supporting Python 3.15! Now you can format code with the `lazy` keyword (PEP 810), and unpacking in comprehensions (PEP 798) 🚀
https://github.com/psf/black/releases/tag/26.5.0
#Black #Python #Python315 #PEP810 #PEP798 -
Black 26.5.0 is out supporting Python 3.15! Now you can format code with the `lazy` keyword (PEP 810), and unpacking in comprehensions (PEP 798) 🚀
https://github.com/psf/black/releases/tag/26.5.0
#Black #Python #Python315 #PEP810 #PEP798 -
Black 26.5.0 is out supporting Python 3.15! Now you can format code with the `lazy` keyword (PEP 810), and unpacking in comprehensions (PEP 798) 🚀
https://github.com/psf/black/releases/tag/26.5.0
#Black #Python #Python315 #PEP810 #PEP798 -
Black 26.5.0 is out supporting Python 3.15! Now you can format code with the `lazy` keyword (PEP 810), and unpacking in comprehensions (PEP 798) 🚀
https://github.com/psf/black/releases/tag/26.5.0
#Black #Python #Python315 #PEP810 #PEP798 -
Black 26.5.0 is out supporting Python 3.15! Now you can format code with the `lazy` keyword (PEP 810), and unpacking in comprehensions (PEP 798) 🚀
https://github.com/psf/black/releases/tag/26.5.0
#Black #Python #Python315 #PEP810 #PEP798 -
The Story of Python's Lazy Imports: Why It Took Three Years and Two Attempts
#Python #PEP810 #LazyImports #CPython #Performance #SoftwareEngineering #MetaCinder #Python315 #StartupTime #TechnicalDeepDive
-
The Story of Python's Lazy Imports: Why It Took Three Years and Two Attempts
#Python #PEP810 #LazyImports #CPython #Performance #SoftwareEngineering #MetaCinder #Python315 #StartupTime #TechnicalDeepDive
-
The Story of Python's Lazy Imports: Why It Took Three Years and Two Attempts
#Python #PEP810 #LazyImports #CPython #Performance #SoftwareEngineering #MetaCinder #Python315 #StartupTime #TechnicalDeepDive
-
The Story of Python's Lazy Imports: Why It Took Three Years and Two Attempts
#Python #PEP810 #LazyImports #CPython #Performance #SoftwareEngineering #MetaCinder #Python315 #StartupTime #TechnicalDeepDive
-
The Story of Python's Lazy Imports: Why It Took Three Years and Two Attempts
#Python #PEP810 #LazyImports #CPython #Performance #SoftwareEngineering #MetaCinder #Python315 #StartupTime #TechnicalDeepDive
-
> Why did you choose `lazy` as the keyword name?
> Not “why”… memorize! :) -
> Why did you choose `lazy` as the keyword name?
> Not “why”… memorize! :) -
> Why did you choose `lazy` as the keyword name?
> Not “why”… memorize! :) -
> Why did you choose `lazy` as the keyword name?
> Not “why”… memorize! :) -
> Why did you choose `lazy` as the keyword name?
> Not “why”… memorize! :) -
Lazy imports are coming to Python :tada:
PEP 810: Explicit lazy imports - PEPs - Discussions on Python.org
https://discuss.python.org/t/pep-810-explicit-lazy-imports/104131/466 -
The Steering Council has accepted PEP 810 (explicit lazy imports) for Python 3.15!
https://discuss.python.org/t/pep-810-explicit-lazy-imports/104131/466
-
I benchmarked `--help` on one of my CLIs with the reference implementation for PEP 810 (Explicit lazy imports).
Because my CLI already does the "inline imports" thing of moving them into functions just before they get used, I got a speedup of x1.3.
Then I moved all the imports to the top like normal, and got a speedup of x2.9!
https://hugovk.dev/blog/2025/lazy-imports/
#Python #Python315 #PEP810 #LazyImports #lazy