python/cpython - Open Source PR Review Scorecard

The Python programming language

C-Rank Grade: A (Welcoming) - 65/100

External PR Merge Rate: 74%

Response Time: 17h

First Timer Success: 47%

Frequently Asked Questions

Is python/cpython welcoming to first-time open-source contributors?

python/cpython has a recorded first-timer success rate of 47.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.

How fast can I expect code review feedback on my pull request?

Maintainers in python/cpython respond to incoming external pull requests in approximately 16.9 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 64.7 C-Rank™ score (A Tier) represent?

The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 64.7 places python/cpython in the A tier.

What is the external contributor pull request merge rate for python/cpython?

The external contributor pull request merge rate for python/cpython is 74.0%, based on public PR activity from non-core contributors.

Are there Good First Issues available in python/cpython?

python/cpython currently has 5 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

python
python/cpythonAWelcoming75.3k
GitHub
Back to Explorer
python

python/cpython

75,284
AWelcoming(65/100)Python

The Python programming language

Compare
Jump to:

AI Maintainer Review Guidelines

Review Persona

Welcoming Community Builder

Warmth Score
8.3/10
Patience Score
8.4/10
Nitpick Rate
40%

Highly welcoming maintainers in python/cpython. Prompt code reviews with positive guidance for new contributors.

Top PR Submission Do's

  • Ensure code complies with the project coding style
  • Keep PRs scoped to a single concern
  • Include context and link to the related issue

Top PR Friction Pitfalls (Don'ts)

  • Do not submit PRs without linking an issue
  • Do not break existing tests without fixing them
  • Do not mix unrelated refactors in a single PR
Response Velocity
16 hours
Standard maintainer review cycle

Average Response Latency

Tracks hours until a maintainer leaves a review, comment, or PR response.

Merge Efficiency
74.0%
Moderate PR acceptance rate

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
47.0%
Accepts new contributor PRs

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
239 core
Highly collaborative maintainer core
Diagnostic Health HUD
74.0%
Merge Gauge
47.0%
1st-Timer
Community Vibe61/100

Embed C-Rank Badge

Show contributors that your repository actively reviews and merges external pull requests.

GetMerged C-Rank badge for python/cpython
[![GetMerged C-Rank](https://getmerged.abhishekco.de/api/badge/python/cpython)](https://getmerged.abhishekco.de/python/cpython?utm_source=github&utm_medium=badge)

Active Good First Issues (5)

View on GitHub

Documentation (UPDATE: Added multiple suspected errors in code snippets in the documentation and another typo to this initial report in #156233 (comment) as I was OK'd to open a PR but encouraged to expand the scope before sending a fix.) Hello Python team, this is just a typo so I know an issue is not required, but I hope you won't mind if I open one in case someone else wants to include it in a larger typo cleanup PR they are already doing (if no one picks it up after some time and I don't find other typos, I can send a PR). In the latest version of https://docs.python.org/3/howto/mro.html#python-2-3-mro (archived as is at https://web.archive.org/web/20260822145356/https://docs.python.org/3/howto/mro.html#python-2-3-mro ) In the sentence Then repeat the operation until all the class are removed or it is impossible to find good heads. it seems "all the class" should be "all the classes". Thanks so much! Linked PRs gh-156320 gh-156475

📅 Opened Aug 22, 2026💬 6 comments
Quality: 90/100Contribute

Documentation PyUnicode_DecodeCharmap has a mapping argument that either takes a mapping or a str: cpython/Objects/unicodeobject.c Lines 8826 to 8833 in e8158d1 if (PyUnicode_CheckExact(mapping)) { if (charmap_decode_string(s, size, mapping, errors, &writer) < 0) goto onError; } else { if (charmap_decode_mapping(s, size, mapping, errors, &writer) < 0) goto onError; } That it takes a str is not documented: https://docs.python.org/3/c-api/unicode.html#character-map-codecs Linked PRs gh-156147

📅 Opened Aug 20, 2026💬 0 comments
Quality: 50/100Contribute

Documentation The Platforms/ re-organization (gh-146445) moved the Android and Apple build trees to Platforms/Android and Platforms/Apple, and the devguide was updated — but several Doc/ pages still reference the old locations, so their :source: links render as broken GitHub URLs on docs.python.org today: Doc/using/android.rst — five :source: references to Android/... (testbed, README, build.gradle.kts, MainActivity.kt, main_activity.c) Doc/using/ios.rst — Apple/iOS/README.md (×2), the testbed reference (Apple/iOS/testbed; the shared testbed now lives at Platforms/Apple/testbed), and a shell example invoking python Apple/testbed Doc/using/configure.rst — :source:`iOS/README.rst` (moved twice, and the file is Markdown) Unrelated to the move, a few more references point at files that no longer exist: Doc/extending/extending.rst — Objects/pycapsule.c (the implementation is Objects/capsule.c) Doc/library/sys.rst — Objects/lnotab_notes.txt (removed in gh-134690; the locatio

📅 Opened Jul 27, 2026💬 1 comment

Bug report Bug description: The type was colorized as a built-in variable instead of keyword. However, type here is a keyword. CPython versions tested on: CPython main branch Operating systems tested on: No response Linked PRs gh-151700 gh-155958

📅 Opened Jun 14, 2026💬 10 comments
Quality: 55/100Contribute

Documentation This part of the documentation is inaccurate: A platform-specific location: On Windows, the directories C:\TEMP, C:\TMP, \TEMP, and \TMP, in that order As you can see from the implementation, %USERPROFILE%\AppData\Local\Temp and %SYSTEMROOT%\Temp are checked before the rest of the already documented directories: cpython/Lib/tempfile.py Lines 169 to 174 in 3ece6b5 if _os.name == 'nt': dirlist.extend([ _os.path.expanduser(r'~\AppData\Local\Temp'), _os.path.expandvars(r'%SYSTEMROOT%\Temp'), r'c:\temp', r'c:\tmp', r'\temp', r'\tmp' ]) else: dirlist.extend([ '/tmp', '/var/tmp', '/usr/tmp' ]) This has bee

📅 Opened Jun 9, 2026💬 5 comments
Quality: 40/100Contribute
Looking for more Python beginner tasks?Explore Python GFI

Contributor Community Vibe Feedback

Rate what actually matters after opening a pull request here.

Have you contributed to this repo?

Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.

3 ratings required
Maintainer helpfulness
Review speed
Beginner friendliness

Contributor Compatibility & Review Speed Analysis for python/cpython

When evaluating whether to contribute to python/cpython, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.

Currently, maintainers of python/cpython acknowledge new external contributions in approximately 16 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 74.0% were successfully merged into the primary branch.

Frequently Asked Questions - Contributing to python/cpython

01

Is python/cpython welcoming to first-time open-source contributors?

python/cpython has a recorded first-timer success rate of 47.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.

02

How fast can I expect code review feedback on my pull request?

The initial maintainer response time averages ~16 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 64.7 C-Rank™ score represent?

The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 64.7 places python/cpython in the Welcoming tier.

04

What is the external contributor pull request merge rate for python/cpython?

The external pull request merge rate is 74.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.

05

Are there beginner Good First Issues open in python/cpython?

Yes, python/cpython currently has 5 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for python/cpython are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.