facebookincubator/metapython

This is Meta's fork of the CPython runtime. The name "cinder" here is historical, see https://github.com/facebookincubator/cinderx for the Python extension...

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 1 hour ago
Added to GitGenius on September 18th, 2026
Created on March 16th, 2021
Open Issues & Pull Requests: 31 (+0)
GitHub issues: Enabled
Number of forks: 139
Total Stargazers: 3,793 (+0)
Total Subscribers: 54 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 14.6 hours
Mean response time: 199.3 days
90th percentile: 967.0 days
Tracked items: 6

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 4
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 708 days
Stale 30+ days: 4
Stale 90+ days: 4

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Metapython is a fork of the CPython runtime maintained by Meta.

The project represents Meta's customized version of the Python interpreter, built on the CPython codebase. It serves as the foundation for Meta's Python extensions and performance improvements, with related JIT compilation work housed in a separate repository. The fork allows Meta to experiment with runtime modifications and optimizations tailored to their internal use cases while maintaining compatibility with the standard Python build process and toolchain.

Developers considering this fork should understand that it is primarily intended for organizations with specific performance or feature requirements that diverge from upstream CPython. The standard build instructions and configuration options remain consistent with CPython, making it accessible to those familiar with building Python from source. This is most suitable for teams operating at scale who need to customize the Python runtime itself rather than relying solely on extensions or third-party libraries. The separation of JIT compiler work into a distinct project indicates that this fork focuses on runtime modifications while compiler enhancements are developed independently.

The project maintains active synchronization with CPython's development, as evidenced by its tracking of the upstream version numbering scheme. Build infrastructure remains comprehensive, with continuous integration across multiple platforms and build configurations including profile-guided optimization support. The codebase reflects ongoing maintenance aligned with CPython's release cycle and development practices.