What the internet is saying about Python

What the internet is saying about "Python programming 2025"

Caveat: The evidence is thin and mostly off-target. Almost nothing discusses "Python in 2025" as a topic. The dominant story is the Python 3.15 release (items dated Oct 2026). Several GitHub hits look like keyword matches on "2025" in PR or issue numbers, such as [19], [20], [23], [24], [25] and [26]. Most items also show only truncated text, so the conclusions below are tentative.

🟢 Supporters

• •Python 3.15 drew the strongest engagement in the set. The release page scored 318 points and 114 comments on Hacker News [1], and a "What's New" link added 10 points [2].
• •A library maintainer welcomed the release. They said their favorite thing about a new Python release is that it ends support for an older one, here Python 3.10, which lets them drop compatibility work [1].
• •Free-threading ecosystem work is moving. The same commenter highlights the new "abi3t" stable ABI for the free-threaded build. Petr Viktorin did most of the CPython implementation, and the commenter has been working to get ecosystem support ready. They call it "rewarding but quite challenging" [1].
• •Performance interest is high. "How Fast is Python 3.15?" got 79 points and 56 comments [3]. The excerpt doesn't show its conclusions.
• •Python hobby and niche projects get attention. "Python on My Wrist" reached 95 points [10], and a Python EDIFACT parser built on syntax trees was posted [11]. A 2025 calculus-in-Python tutorial also circulated [7].
• •Professional tooling practices are being adopted. Examples include gating CI on ruff [5], building an sdist and wheels and publishing to PyPI through Trusted Publishing [8], and tightening Falcon 4 dependency bounds [4].

🔴 Skeptics

• •The 3.15 source tarball is larger. One commenter notes the XZ-compressed tarball is "about half again as large as the one for 3.14" [1]. The excerpt cuts off before the explanation.
• •Ecosystem readiness for free-threading takes real effort. The abi3t work was described as "quite challenging" because everything has to be verified as working [1].
• •Lint debt can be large. One repo's CI never ran its configured ruff. On main it reported about 4,900 findings under ruff 0.16's default rules, mostly style, so the PR gates only on correctness families [5].
• •Old Python versions still cause trouble. One fix keeps a script running on Python 3.6+ and adds a notice for users on an end-of-life Python [13].
• •Subprocess handling has pitfalls. subprocess.run kills only the process it started on timeout. A timed-out Bash-script tool left its child git grep running as an orphan [15].
• •Dependency churn is visible. One bot PR bumps 10 pip packages at once, such as python-multipart 0.0.20 → 0.0.31 [6].

⚪ Neutral Observers

• •Python-based security scanning tools are under active bug-fixing. One scanner could report a clean scan for files over 10 MiB it never read [12].
• •Decompilation tooling. A differential behavior check for decompiled programs [14] and a list of open-source decompilers [16] appear, though their link to Python is only partial in the excerpts.
• •Refactoring and maintenance PRs include sharing one CLI layer across seven mill CLIs to remove duplication [9], and a Langfuse Python SDK flush() latency fix [20].
• •Unrelated noise. Items [17], [18], [19], [21], [22], [23], [24], [25] and [26] have little visible Python-specific content.

Cross-Platform Signals

• •Hacker News: Discussion centers on the Python 3.15 release, its speed, and its free-threading ABI work. Other posts are small projects and tutorials. Engagement is highest here.
• •GitHub: Activity is routine engineering. It covers CI and lint gating, packaging and publishing, dependency bumps and bug fixes, with little commentary on Python itself.
• •Consensus and divergence: No direct disagreement appears. Sentiment toward 3.15 is positive or curious, with practical caveats. GitHub shows Python used as everyday infrastructure rather than a debated topic.

Community Verdict

The evidence doesn't capture a "Python 2025" debate. It shows a community focused on the next release, 3.15, with strong interest in speed and free-threading, relief at dropping 3.10, and a bit of grumbling about tarball size and the work needed for ecosystem readiness. Alongside that, projects are tightening linting, packaging and dependency hygiene. Overall the mood is pragmatic and mildly positive, but the sample is small and mostly truncated, so don't over-read it.

---

Based on Hacker News + GitHub data from the last 30 days, researched with last30days by Matt Van Horn.