Skip to content
rsalmei

rsalmei/alive-progress

A new kind of Progress Bar, with real-time throughput, ETA, and very cool animations!

A new kind of Progress Bar, with real-time throughput, ETA, and very cool animations!

6.3k 12 since joining 232PythonPush 18d agoListed 22d ago16 open issuesMIT
aliveanimatedanimationsbarclietafeedbackmonitoring
  • Python99.6%
  • Just0.4%
View on GitHub

Report a problem

1 Review

alive-progress is a polished and unusually thoughtful Python terminal progress-bar project. The value proposition is clear: it is not just a tqdm alternative, but a richer terminal feedback system with animated spinners, real-time throughput, ETA smoothing, print/logging integration, overflow/underflow detection, pause/resume-oriented behavior, and extensive customization. The README is a major strength: it shows demos, installation, core usage, advanced modes, styling, configuration, Jupyter/PyCharm notes, and Python EOL guidance. That makes the project approachable for first-time users while still documenting deeper features for power users.

The repository also shows strong maintenance signals. It has about 6.3k stars, 232 forks, MIT licensing, Python-dominant code, a tests/ directory, noxfile.py test automation across Python 3.9-3.13, package metadata for Python 3.9-3.14, and recent CI/activity around version 3.3.0, typing support, Python 3.14, and dependency maintenance. The open issues and PRs are manageable in size, and several are feature requests or edge-case terminal compatibility reports rather than signs of instability.

The biggest improvement opportunity is contributor onboarding. The README is excellent for users, but a short CONTRIBUTING.md with local setup, test commands, release expectations, style rules, and guidance for terminal-rendering tests would lower the barrier for outside contributors. I would also consider moving some advanced README sections into docs pages so the front page stays easier to scan. Finally, since issue #306 and PR #311 point to typing concerns, tightening public type annotations and adding type-checking to CI would be a high-impact next step for a package used inside other developers’ tooling.