Skip to content
BSWEN
Blog

When Will Python Include Rust Code? Python 3.16 Timeline and Roadmap

Cowrie
Cowrie
Dev @ Bswen

Python Programming

Purpose

I’ve been following the Rust for CPython project and wanted to understand when Python would actually include Rust code in its core implementation. The official announcement from Python Insider in April 2026 provides the roadmap, and the answer is clearer now: Python 3.16 is the target.

What’s the Project About?

The Rust for CPython project is working toward a PEP (Python Enhancement Proposal) that would introduce Rust code into CPython itself. This is different from writing Python extensions in Rust - it’s about Rust becoming part of Python’s core implementation.

Why does this matter? Rust could provide safer, faster core components while keeping Python easy to use. Memory safety and performance improvements are the main goals.

The Timeline

I found the roadmap helpful, so here’s a summary:

Rust for CPython Roadmap 2026
March 2026    → Build system complete (works on all tested CPython platforms)
April 2026    → API design planning, first extension module selected
May 2026      → Internal Rust API implementation begins, PyCon US sprint
June 2026     → PEP writing
July 2026     → PEP submission for community review
May 2027      → Python 3.16 beta (feature freeze)

The original target was Python 3.15, but the team moved it to 3.16. This gives them about one extra year for implementation and PEP discussion before the feature freeze in May 2027.

Current Progress

From the announcement, I noted these milestones:

  • Build system: Now works across all tested CPython platforms in CI
  • Rust team discussions: Productive conversations on CPython integration needs
  • API design: Issues tagged on GitHub for community input
  • Module selection: The first extension module for Rust implementation was selected in April 2026

The PyCon US sprint in May 2026 is planned to work on the internal Rust API. This is a chance for contributors to get involved directly.

What Developers Should Know

The technical implementation details are still internal. The Rust API for public use won’t be stabilized until a future PEP. But if you want to contribute or follow the progress:

  • Join the project Discord
  • Attend weekly Monday meetings
  • Check the GitHub issues tagged for API design
  • Participate in the PyCon US sprint (May 2026)

The Reason for the Delay

I think the key reason for moving from Python 3.15 to 3.16 is the need for thorough review. Introducing Rust into CPython is a significant architectural change. The extra year allows:

  • More time for API design refinement
  • Better PEP discussion with the community
  • Complete testing across all platforms
  • Time to select and implement one extension module properly

The announcement mentions that “productive discussions with the Rust team” happened, suggesting the collaboration is going well. But architectural changes need careful consideration.

Summary

In this post, I explained the Rust for CPython project roadmap. The key point is that Python 3.16 (May 2027 beta) is the target version for Rust code inclusion, with the PEP expected in July 2026. If you’re interested in contributing, join the Discord and weekly meetings.

Final Words + More Resources

My intention with this article was to help others share my knowledge and experience. If you want to contact me, you can contact by email: Email me

Here are also the most important links from this article along with some further resources that will help you in this scope:

Oh, and if you found these resources useful, don’t forget to support me by starring the repo on GitHub!

Comments

Tags: