Glonce

CPython officially adds tier 3 RISC-V support

toolsThe Glonce editorsHacker News🔥52Glonce rating52Impact65Novelty65Relevance75Surprise40Players65Credibility85
CPython officially adds tier 3 RISC-V support

CPython, the standard Python interpreter, has officially added tier 3 platform support for RISC-V. The post's author describes months of work improving CPython's support for the architecture, and frames tier 3 status as recognition that the platform has reached the point where it could be added to PEP 11, the document CPython uses to track which platforms it officially supports. The announcement was published on the official Python blog.

RISC-V is an open instruction set architecture (ISA). Unlike proprietary ISAs such as x86 and ARM, it is developed as an open standard that anyone can implement. Its ecosystem has grown considerably in recent years and is projected to quadruple by 2032, which the post gives as the reason it matters for Python to work reliably on RISC-V platforms.

Getting to tier 3 relied on community contributions: people testing CPython on real RISC-V hardware, fixing architecture-specific issues, improving build support, filing bug reports, and reviewing patches. A particularly important piece was reliable, ongoing testing on real hardware. The RISE Project provided several RISC-V machines, giving CPython buildbots for testing as well as for debugging architecture-specific issues. The post thanks Ludovic Henry from the RISE Project, Furkan Onder, and Emma Smith by name, along with many other contributors, and says a fellowship from the Sovereign Tech Agency personally supported the author's own work on this.

The post lays out what comes next: bringing RISC-V testing directly into CPython's continuous integration, again supported by RISE through its RISE RISC-V Runners initiative, so contributors get faster feedback than the current buildbots, which usually run only after a patch has already merged, and so RISC-V-specific problems can be caught earlier. The long-term goal is to promote RISC-V from tier 3 to tier 2 support. The post also mentions exploring architecture-specific optimizations to make better use of RISC-V's capabilities, and it asks anyone with access to RISC-V hardware to build and run CPython, run their own workloads and test suites, and report what breaks. It closes by noting that CPython is only one part of the Python ecosystem, and that continued community work across packages, compilers, tooling, and infrastructure will still be needed to make RISC-V a well-supported platform for Python as a whole.

Key facts

  • CPython has been granted tier 3 platform support for RISC-V under PEP 11, the document CPython uses to track which platforms it officially supports.
  • RISC-V is an open instruction set architecture that anyone can implement, unlike proprietary ISAs such as x86 and ARM, and its ecosystem is projected to quadruple by 2032.
  • The RISE Project supplied several RISC-V machines, giving CPython buildbots for testing and for debugging architecture-specific issues.
  • Named contributors include Ludovic Henry from the RISE Project, Furkan Onder, and Emma Smith; a Sovereign Tech Agency fellowship personally supported the post's author.
  • Next steps include bringing RISC-V testing directly into CPython's CI through RISE's RISC-V Runners initiative, with a long-term goal of promoting RISC-V from tier 3 to tier 2 support.

Why it matters

Tier 3 is a formal designation under PEP 11, the document CPython uses to record which platforms it officially supports, so the change moves RISC-V from best-effort community support to an officially recognized platform. RISC-V is an open instruction set architecture: unlike proprietary ISAs such as x86 and ARM, it is developed as an open standard that anyone can implement, and its ecosystem is projected to quadruple by 2032. The post frames that growth as the reason it matters for Python to work reliably on these platforms.

Who it affects

Anyone running or planning to run Python on RISC-V hardware gains an officially recognized CPython rather than one supported only informally by the community. The RISE Project, which supplied the RISC-V machines and buildbots behind the testing, and the Sovereign Tech Agency, whose fellowship funded the author's own work, are both named as backers. Individual contributors credited include Ludovic Henry from RISE, Furkan Onder, and Emma Smith, alongside many others who tested hardware, fixed issues, and reviewed patches. The post also points beyond CPython itself to the wider Python ecosystem, packages, compilers, and tooling, which it says still needs continued community work before RISC-V is well supported for Python as a whole.

How to use it

There is no product, price, or license attached to this change: it is a platform-support status update to the interpreter itself. The practical call to action is for testing: the post asks anyone with access to RISC-V hardware to build and run CPython on it, run their own workloads and test suites, and report whatever breaks. That feedback is what the project says it needs to strengthen tier 3 support and build toward eventually promoting RISC-V to tier 2.

How solid is it

This account comes directly from the official Python blog, written in the first person by the CPython contributor who did the work, rather than from third-party reporting. That is about as close to a primary source as this kind of claim gets: it is the project confirming a change to its own platform-support policy, and it names the organizations and people behind the testing, the RISE Project's buildbots, the Sovereign Tech Agency's fellowship, and individual contributors by name. On Hacker News the story drew a modest 78 points and 13 comments, consistent with a technical infrastructure milestone rather than a contested claim. The post is also careful about what is not yet finished: it describes CI integration as something the project is 'currently investigating,' not something already done, and it calls reaching tier 2 only a long-term goal.

Risks and caveats

Tier 3 is not yet backed by CPython's continuous integration: today's testing runs through separate buildbots that report failures only after a patch has already been merged, so a RISC-V regression can land before anyone catches it. Moving that testing into CI, and moving RISC-V up to tier 2, are both described only as goals, with no committed timeline for either. The post does not name a target CPython version for this change, give an exact date for the PEP 11 update, or say which RISC-V hardware variants or how many buildbots the RISE Project provided. It also treats current testing coverage as incomplete, asking readers with RISC-V hardware to run their own workloads and report what breaks, and it notes that packages, compilers, and tooling across the rest of the Python ecosystem still need work before RISC-V is well supported beyond CPython itself.

“Its ecosystem has grown considerably in recent years and is projected to quadruple by 2032.”

— the CPython blog post announcing tier 3 RISC-V support