I’m happy to announce that the Steering Council has approved my proposal to hold the next Language Summit at @europython 2026 and then alternate with @pycon US!
The EuroPython Society plan to announce the location and date in the new year, stay tuned.
https://discuss.python.org/t/language-summit-at-europython-2026/105355
https://ep2026.europython.eu
#Python #LanguageSummit #EuroPython

Language Summit at EuroPython 2026
Following on from this topic and this poll, I’m happy to announce that the Steering Council has approved having the next Language Summit at EuroPython 2026! The EuroPython Society plan to announce the location and date in the new year, stay tuned.
Discussions on Python.org🔒 #Python #security news:
We're going to start disabling the commit bit (aka write access) to the #CPython repo for inactive core team members.
https://discuss.python.org/t/regularly-disabling-unused-commit-access-to-the-cpython-repo/105010
I proposed this after a security discussion at last year's #LanguageSummit:
https://pyfound.blogspot.com/2024/06/python-language-summit-2024-python-security-model-after-xz.html
Disabling the commit bit has no impact on core team status, nor Steering Council voting status, and you can easily ask for it back again.

Regularly disabling unused commit access to the cpython repo
Howdy committers - The Python Steering Council (PSC) has had an open issue based on discussions last year to improve our project’s security posture. We’re going to move forward with disabling GitHub commit privileges for inactive core team members. This has no impact on “core team” or “Python Steering Council (PSC) voting” status. It is merely a good security practice to not leave unused credentials laying around. Seth (Security Developer-in-Residence) lays out the rationale here. How do we...
Discussions on Python.orgAt 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)
Should Python adopt CalVer?
Python 3.26, 26.0 or 26.10? Language Summit, PyCon US, Pittsburgh, 2024-05-15.
Some more photos from yesterday's Language Summit. We had a full day of short talks followed by discussion.
The schedule:
https://us.pycon.org/2024/events/language-summit/#PyConUS #PyCon #Python #LanguageSummit- Language Summit
- PyCon US 2024
I just kicked off PyCon 2024 with the first talk of the Language Summit (and my first talk at PyCon!): "Should Python adopt CalVer?" It was an interesting discussion, let's see!
#PyConUS #PyCon #Python #CalVer #CalendarVersioning #LanguageSummit