🐍🏃‍➡️🏃‍➡️🏃‍➡️🏃‍➡️ #Python #CoreDevSprint Thursday highlights:

* I submitted #PEP2026 (Calendar versioning for Python) to the steering council for consideration!

* Update from Brandt Bucher on the #JIT compiler. We're heading in the right direction: “We went from 0% slower to 0% faster”

* I gave yesterday's @HelPy quiz. Most incorrect answer was a pleasant surprise: we've had ~400 new contributors to 3.13!

* Magic by Pablo Galindo Salgado

* A tour of the Meta office. Big thanks to Meta for hosting us!

🐍📅 At 20:26 Helsinki time on the 26th, I submitted PEP 2026 (calendar versioning for Python) to the steering council for consideration! 🤞

https://github.com/python/steering-council/issues/255

#Python #CalVer #CalendarVersioning #PEP2026

PEP 2026 -- Calendar versioning for Python · Issue #255 · python/steering-council

Please consider PEP 2026 -- Calendar versioning for Python https://peps.python.org/pep-2026/ The PEP has been discussed in threads listed in its Post-History header The PEP was announced on Discuss...

GitHub

At 20:26 this evening I published PEP 2026 to propose Python adopts calendar versioning!

https://peps.python.org/pep-2026/

This means that starting with the 2026 release, the version will be 3.YY.micro; Python 3.15 will cease to be, and will instead be Python 3.26.

Discuss:

https://discuss.python.org/t/pep-2026-calendar-versioning-for-python/55782

Read @sethmlarson's blogpost of my Language Summit talk:

https://pyfound.blogspot.com/2024/06/python-language-summit-2024-should-python-adopt-calver.html

#PEP2026 #Python #PyConUS #PyCon #CalVer #CalendarVersioning #LanguageSummit

PEP 2026 – Calendar versioning for Python | peps.python.org

This PEP proposes updating the versioning scheme for Python to include the calendar year.

Python Enhancement Proposals (PEPs)