ggpy vs Lets-Plot
A data-driven comparison of two Python grammar of graphics & declarative plotting libraries: popularity, development activity, licensing and installation. Updated .
Key differences
- ggpy has 2.1× as many GitHub stars as Lets-Plot (3.7K vs 1.8K).
- Lets-Plot had more development activity over the last 12 months: 511 commits vs 0.
- ggpy is downloaded 1.7× as often on PyPI (20.2K vs 11.7K per week).
- ggpy is licensed under BSD-2-Clause; Lets-Plot under MIT.
- ggpy is written primarily in Python, Lets-Plot in Kotlin.
- ggpy is the older project: its repository was created in 2013, Lets-Plot's in 2019.
- ggpy's repository is archived, so it no longer receives updates.
By the numbers
- ggpy
- Lets-Plot
Show data as a table
| Metric | ggpy | Lets-Plot |
|---|---|---|
| GitHub stars | 3,688 | 1,783 |
| PyPI downloads / week | 20,211 | 11,722 |
| Commits, last 12 months | 0 | 511 |
| Contributors | 12 | 21 |
| Forks | 559 | 63 |
Development activity
Commits per month to each default branch, last 12 complete months.
- ggpy
- Lets-Plot
Show data as a table
| Month | ggpy | Lets-Plot |
|---|---|---|
| Nov 2025 | 0 | 45 |
| Dec 2025 | 0 | 45 |
| Jan 2026 | 0 | 62 |
| Feb 2026 | 0 | 115 |
| Mar 2026 | 0 | 54 |
| Apr 2026 | 0 | 79 |
| May 2026 | 0 | 77 |
| Jun 2026 | 0 | 34 |
| Jul 2026 | 0 | 0 |
| Aug 2026 | 0 | 0 |
| Sep 2026 | 0 | 0 |
| Oct 2026 | 0 | 0 |
Side by side
| Attribute | ggpy | Lets-Plot |
|---|---|---|
| Description | Plotting system based on R's ggplot2. | Grammar of graphics plotting library for Python and Kotlin, by JetBrains. |
| Category | Python grammar of graphics & declarative plotting libraries | Python grammar of graphics & declarative plotting libraries |
| License | BSD-2-Clause | MIT |
| Language | Python | Kotlin |
| Status | Archived | Maintained |
| Latest release | – | v4.11.0 () |
| Last commit | ||
| Repository created | ||
| Open issues | 147 | 144 |
| Install | pip install ggplot | pip install lets-plot |
Which should you choose?
Popularity and activity are only part of the story. Consider which ecosystem you work in, the chart types and interactions you need, how much data you render, and whether the license fits your project. Both tool pages list alternatives if neither is quite right.