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.

https://github.com/numpy/numpy/issues/30416#issue-3718116466

This is the saddest news I’ve heard recently: #PyPy is no longer under active development.

It is so bad to know that [they originally did not intend to go beyond 3.10](https://github.com/orgs/pypy/discussions/5145#discussioncomment-13121917).

#Python

just used #PyPy to accelerate an Amaranth simulation from 35s to 17s (no code changes)

it's pretty good