The Python version diagram has been updated to show the bugfix/security split for each release. (Before, the bars were either completely green or yellow.)

https://devguide.python.org/versions/

It's also zoomed in and shows fewer releases than before. There's another chart further down the page showing all of 2.6 to 3.14. And the wording in the status key has been refreshed to make it clearer.

Thanks to @nedbat and @encukou for updating it!

CPython C API: 5 вопросов на собеседовании

Привет, Хабр! В этой статье разберём несколько вопросов на собеседованиях, связанных с устройством CPython и его C API.

https://habr.com/ru/companies/otus/articles/890378/

[Перевод] Производительность интерпретатора Python 3.14 с оптимизацией хвостовых вызовов

Примерно месяц назад проект CPython смерджил новую стратегию реализации интерпретатора байт-кода. Первоначальные результаты были очень впечатляющими , продемонстрировав среднее повышение производительности на 10-15% в широком спектре бенчмарков на различных платформах.

https://habr.com/ru/companies/ruvds/articles/891562/

Following git blame in CPython can quickly take you a long way back!

3 years ago
23 years ago
25 years ago
32 years ago
32 years ago (+ 6 days)

(Checking who first added these tests, it was Guido on 9th March 1994 for Python 2.0.)

https://github.com/python/cpython/blame/83125775e0a5c5088da0cb62b43e7cfd8a04fdc6/Lib/random.py

https://github.com/python/cpython/commit/ff03b1ae5bba4d6712563efb7c77ace57dbe6788

Performance of the #Python 3.14 tail-call interpreter- About a month ago, the #CPython project merged a new implementation strategy for their bytecode interpreter. The initial headline results were very impressive, showing a 10-15% performance improvement on average across a wide range of benchmarks across a variety of platforms.

Unfortunately, as I will document in this post, these impressive performance gains turned out to be primarily due to inadvertently working around a regression in #LLVM 19. When benchmarked against a better baseline (such GCC, clang-18, or LLVM 19 with certain tuning flags), the performance gain drops to 1-5% or so depending on the exact setup.

https://blog.nelhage.com/post/cpython-tail-call/

Под чешуёй асинхронности: from yield to await

В данной статье мы рассмотрим основы асинхронного программирования в python, фокусируясь на ключевых концепциях и их практическом применении. Мы начнем с изучения генераторов и итераторов — фундаментальных механизмов, лежащих в основе асинхронности python. Затем поговорим о потоках и процессах, чтобы понять, как они соотносятся с асинхронным подходом. Основная цель статьи — создание собственной упрощенной реализации asyncio, включая цикл событий, задачи и примитивы синхронизации. Это позволит глубже понять внутреннее устройство асинхронной разработки в python.

https://habr.com/ru/articles/889490/

Performance of the Python 3.14 tail-call interpreter — https://blog.nelhage.com/post/cpython-tail-call/
#HackerNews #Python #Performance #TailCall #Interpreter #CPython #3.14 #Programming

I'm trying to compile CPython with the mold(1) linker, but so far I haven't been able to get the build system to pick it up. Can anyone point me in the direction of building CPython with mold(1).

This isn't for any purpose other than playing around/learning.

If anyone is willing, I'd appreciate a boost for visibility :)

#Slixmpp 1.9.0 has been released (#XMPP / #Jabber / #SleekXMPP / #Python / #CPython) https://slixmpp.readthedocs.io/

New account, so new #introduction. Let's do it again!

I have a #MastersDegree in #ComputerScience and #ComputerEngineering. I went to #NMU for undergrad and #MSU for my graduate degree. I currently work at #UChicago for the #TMWCenter, which focuses on helping young children acquire language (and therefore other learning skills) faster.

In my spare time, I develop #OpenSourceSoftware such as
- a #SphinxDoc extension that embed #Fediverse comments on your page
- a library to talk to #ManifoldMarkets from native #Python
- a #PredictionMarket manager using the above
- a #transpiler from a subset of Python to #OpenStreetMaps's #OverpassQL
- bug fixes to many other projects, including #mypy, #base58, #attrs, #CPython, & more

I spend a fair bit of my time these days on #MathResearch, specifically into the #ThueMorse Sequence and its extensions.

I'm also a hobbyist editor on OpenStreetMap.

#Demisexual, #transfem, and happily engaged to my #enby sweetheart.

We have two cats: #OpheTheLoaf and #MayalaranTheCat (yes, from #StormlightArchive) See here for more on them!

I speak English fluently, Spanish haltingly, and am trying to learn Chinese

#queer #Chicago

Moim zdaniem, polityka projektu #CPython dotycząca starszych wersji otrzymujących wyłącznie "poprawki bezpieczeństwa" nie sprawdza się.

W praktyce sprowadza się do tego, że mamy kilka starszych gałęzi, które rzekomo są wspierane, użytkownicy polegają na tym wsparciu, a w rzeczywistości wsparcia nie ma, więc dystrybucje muszą samemu zaciągać łatki po to, by naprawiać problemy z tymi wersjami. Włączając w to poprawki bezpieczeństwa, które jeszcze nie doczekały się wydania w tych gałęziach.

(Tutek sponsorowany przez konieczność zaciągnięcia kolejnego zestawu paczek do #Gentoo.)

I think the #CPython approach of "security supported" releases is pretty bad.

It basically means that there's a bunch of versions that upstream pretend to support and users rely on being supported, except that they aren't really supported, so downstreams have to do all the work backporting patches to fix bugs. Including security bugs that haven't made it into a release yet.

(Post sponsored by yet another bunch of patches being backported in #Gentoo.)

Been working with Python for the past 6 years, and I just landed my first PR to CPython! Super excited to contribute to my favorite programming language and looking forward to making more contributions.

https://github.com/python/cpython/pull/130253

#Python 3.14 se dote d'un interpréteur plus performant (mais pas disponible dans toutes les versions de #CPython car ça dépend du compilateur utilisé). Avec des gains qui semblent comparable à ceux qu'on a pu voir avec Python 3.11 (10% ou mieux)
@simon regroupe des liens sur comment c'est arrivé et comment tester la version alpha dès aujourd'hui :
https://simonwillison.net/2025/Feb/13/python-3140a5/

Jeżeli kiedyś zastanawialiście się, jak szybko rośnie `packaging.tags.sys_tags()` na GNU / #Linux, to mam formułkę (chyba że coś popieprzyłem). Dla #CPython 3.x na #glibc 2.y, łączną liczbę tagów wyraża wyrażenie:

2xy + x + 3y + 3

Albo równoważnie:

x(2y + 1) + 3y + 3
y(2x + 3) + x + 3

Co za tym idzie, jeżeli nic innego się nie zmienia, to każda nowa wersja Pythona dodaje (2y + 1) tagów, a każda nowa wersja glibc dodaje (2x + 3) tagów. Dla glibc 2.41, daje to 83 nowe tagi na nową wersję CPythona. Dla CPythona 3.13, mamy 29 nowych tagów na nową wersję glibc.

No i dla porównania: CPython 3.13 na architekturze x86_64 z glibc 2.41 ma już 1205 zgodnych tagów paczek wheel.

If you were ever wondering how fast `#packaging.tags.sys_tags()` are growing on GNU / #Linux, I have a formula for you (unless I screwed up the maths). For #CPython 3.x on #glibc 2.y, the total number of tags is:

2xy + x + 3y + 3

Or equivalently:

x(2y + 1) + 3y + 3
y(2x + 3) + x + 3

So all other things equal, every new minor version of #Python introduces (2y + 1) tags, and every new minor version of glibc introduces (2x + 3) tags. For glibc 2.41, this means 83 new tags per CPython version. For CPython 3.13, this means 29 new tags per glibc version.

Oh, and for a good measure: CPython 3.13 on x86_64 with glibc 2.41 features 1205 compatible wheel tags.

Just released: Python 3.14.0a5 discuss.python.org/t/python-3-1... docs.python.org/3.14/whatsne... Also recently released! blurb 2.0.0 cherry-picker 3.5.0 pypistats 1.8.0 PrettyTable 3.13.0 & 3.14.0 tox-dev/action-pre-commit-uv 1.0.2 em-keyboard 5.0.0 #Python #CPython #Python314 #release

Python 3.14.0 alpha 5