There's been a noticeable increase in PyPy development activity in the last couple of months. Makes me very happy.

A lot of that comes from new energy from @stanfromireland, the newest PyPY core developer. But it also seems @mattip and @cfbolz are more active too, and users seem to be filing more issues and even proposing more PRs.

I can't explain this uptick in activity, any theories?

#Python #PyPy

#gentoo plans to switch from Python 3.13 to πthon 3.14 on 2026-06-01. https://www.gentoo.org/support/news-items/2026-04-16-python3-14.html

"Other πthon implementations
============================
At the same time, we are also going to remove the target support for πthon 3.11 (πthon3_11) and ππ 3.11 (ππ3_11). Since there are
no plans to release a πthon 3.12-compatible ππ version yet, Gentoo will be removing ππ support for the time being."
:-(

#PyPy

PyPy v7.3.22

PyPy 7.3.22 버전이 출시되어 Python 2.7과 3.11 인터프리터를 지원하며, 주요 JIT 버그 수정과 CPython 호환성 개선이 포함되었습니다. 특히 RPython _pickle 모듈과 json 인코더가 도입되어 피클링과 JSON 처리 속도가 크게 향상되었고, 멀티프로세싱 환경에서의 성능도 개선되었습니다. 이번 마이크로 릴리스는 기존 7.3 시리즈와 API 호환성을 유지하며, PyPy의 빠른 JIT 컴파일러 기반 성능을 더욱 강화합니다. PyPy는 다양한 플랫폼 바이너리를 제공하며, 개발자 커뮤니티 참여와 C 확장 라이브러리의 HPy/CFFI 변환을 권장하고 있습니다.

https://pypy.org/posts/2026/04/pypy-v7322-release.html

#pypy #python #jit #rpython #performance

PSA: The annual #Gentoo #Python switch planned for 2026-06-01. CPython 3.14 becomes the default, 3.11 and #PyPy 3.11 go out. The latter fills me with sadness but keeping it is unrealistic now that projects are aggressively pushing for 3.12+.

Of course, we'll continue shipping the interpreters, so you can use venvs if you like. However, that's going to become harder to use since many projects either don't ship PyPy wheels or don't work on PyPy at all without patching.

We will revisit PyPy support if a version compatible with Python 3.12 appears in reasonable time.

https://public-inbox.gentoo.org/gentoo-dev/[email protected]/T/#u
https://public-inbox.gentoo.org/gentoo-dev/[email protected]/T/#u

I was already having misgivings about #CPython when I saw a required #Rust dependency coming up (although I know many here have no issues with this), but now that there have been #LLM commits to the project, I'd like to look at alternatives. It seems great that #Pypy exists, although I worry that it will end up replicating undesirable behavior from CPython in the future.

I had been learning C++ with the goal of writing extensions using CPython. As it happens, I already have a physical copy of a book on #Lua and many applications are written in C++ with Lua scripting on top, so I'm going to swap out Python for Lua in an upcoming project. I'm excited to be able to experiment with #LuaLaTeX or writing scripts for #GeanyIDE. The language shows up in way more places than I realized.

#Python #cpp #CPlusPlus #programming #Scripting #ScriptingLanguage #TexLatex

https://blog.gslin.org/archives/2026/03/19/12941/%e5%be%88%e5%a4%9a-python-%e5%8a%a0%e9%80%9f%e7%9a%84%e6%96%b9%e6%b3%95/

很多 Python 加速的方法

#c #code #codon #compiler #cpython #cython #graalpy #jax #mojo #mypyc #native #numba #numpy #performance #pyo3 #pypy #python #rust #speed #taichi

With CPython now actively merging "AI" slop in the form of co-authored commits from Anthropic Claude… I'm leery about starting new projects atop the reference #Python implementation.

My projects remain slop-free at this point in time, and it is my intention that they stay that way. I can't afford the legal risk that comes with them: a machine cannot represent itself in court, therefore a machine cannot be held accountable for infractions of copyright law. This means the buck stops with the humans.

Cursory glance at Pypy, it is compatible with Python 3.11 and, on the surface, does not show any co-authored commits. I've used it in the past and found it to be mostly compatible.

Is it good enough for a fork? Did I miss something?

https://github.com/pypy/pypy

#Pypy #Pypy3 #NoAI

Python Standard Library для спортивного программирования

Стандартная библиотека Python содержит множество инструментов, которые значительно упрощают решение задач спортивного программирования, но многие из них остаются незамеченными начинающими участниками. В статье собран краткий конспект по наиболее полезным модулям и функциям стандартной библиотеки с небольшими примерами.

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

#спортивное_программирование #питон #python #pypy #standard_library #стандартная_библиотека #стандартная_библиотека_python #icpc #codeforces #topcoder

Even a decade back, when #PyPy was showing promising performance benefits of 4x speedup or even more, it was of little benefit to an increasingly compiled scientific stack. PyPy was only useful in a Pure Python environment, so I am not surprised with its removal from #NumPy

https://github.com/numpy/numpy/issues/30416

However I am genuinely surprised to hear that PyPy as a project is "no longer under active development, and has not released a Python3.12 version." I think the emphasis is on the latter, that it takes time for PyPy to catch up to Python 3.12 and due to NEP29 they should only support Python 3.12+.

https://numpy.org/neps/nep-0029-deprecation_policy.html

I haven't seen an official announcement of PyPy being discontinued and would refuse to believe that until I see one.