Post #1056565
2026-04-06 20:21 UTC
Systematically reviewing Python C extensions (575+ bugs found so far) and offering to analyze yours!
I’ve recently analyzed 44 C extensions for correctness and free-threading readiness. I'd love to run the analysis on your extension too.
If you want the deep dive into the methodology, the false positive rates, and what I've learned, I wrote a full post here: https://discuss.python.org/t/systematically-finding-bugs-in-python-c-extensions-575-confirmed-so-far/106875
But if you just want your C extension checked, reply below or DM me!
#Python #CPython
Replies (2)
-
@danzin@mastodon.social 2026-04-06 20:33
Historically, automated bug-finding tools have a bad habit of producing high-noise findings (and now worse: convincing AI slop) that just wastes maintainer time. I built `cext-review-toolkit` using multiple specialized agents to find bugs, and I try to reproduce every finding from pure Python before reporting it. Human review + pure-Python reproducers act as a necessary filter against false positives. #Python #CPython
-
@adamchainz@fosstodon.org 2026-04-07 09:03
@danzin please check my time-machine and tprof packages, and if you can do C++ too, icu4py. Great work, cheers!!