Live coding in Python with PyCharm, Emacs, Sublime Text, or even a browser
C-Rank Grade: B (Solid) - 47/100
External PR Merge Rate: 87%
Response Time: 8h
First Timer Success: -
donkirkby/live-py-plugin has a recorded first-timer success rate of 0.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in donkirkby/live-py-plugin respond to incoming external pull requests in approximately 7.6 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
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 46.6 places donkirkby/live-py-plugin in the B tier.
The external contributor pull request merge rate for donkirkby/live-py-plugin is 86.8%, based on public PR activity from non-core contributors.
donkirkby/live-py-plugin currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in donkirkby/live-py-plugin welcoming community pull requests and bug fixes.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/donkirkby/live-py-plugin?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 04:00 UTC (04:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 01:00 to 05:00 UTC (01:00 - 05:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~5 hours (96% approval). Large PRs (>500 lines) take ~36 hours (39% approval). Keep your diff compact for rapid review.
We have LiveImageDiffer for comparing images and LiveFigure for displaying Matplotlib figures in live coding mode. Derive LiveFigureDiffer as a subclass, and override create_painters() to create two figures. Make sure it gracefully degrades when Matplotlib is not available. Make LiveImageDiffer work with LiveImage, and convert them to LivePainter when needed. Add create_figures() method to LiveFigureDiffer to help with type checking. Another option is to make LiveImageDiffer a generic class that can compare any subtype of LiveImage.
What I did When you use the LiveImageDiffer, particularly with text in images, the images are sometimes a little unpredictable. For example, antialiasing can make random changes to the text pixels. What happened You can use the tolerance attribute to allow some difference, but the pattern is usually a small number of pixels with a significant difference, and most pixels with no difference. Tolerating difference in the text pixels could mask differences in a lot of other pixels, elsewhere in the image. What could happen Matplotlib's check_figures_equal() takes a tolerance paramter, but compares it to the root mean square of the colour difference of all pixels in the image. We could either add another tolerance attribute or switch what the current one means. Probably better to add a new one, instead of breaking some old tests.
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to donkirkby/live-py-plugin, 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 donkirkby/live-py-plugin acknowledge new external contributions in approximately 7 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 86.8% were successfully merged into the primary branch.
donkirkby/live-py-plugin has a recorded first-timer success rate of 0.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~7 hours. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
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 46.6 places donkirkby/live-py-plugin in the Solid tier.
The external pull request merge rate is 86.8%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, donkirkby/live-py-plugin currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for donkirkby/live-py-plugin 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.