July 1st, 2024

Announcing Polars 1.0 (Blog Post)

Polars releases Python version 1.0 after 4 years, gaining popularity with 27.5K GitHub stars and 7M monthly downloads. Plans include improving performance, GPU acceleration, Polars Cloud, and new features.

Read original articleLink Icon
Announcing Polars 1.0 (Blog Post)

Polars has announced the release of version 1.0 for Python, marking a significant milestone after four years of development. The project has gained popularity with 27.5K GitHub stars and 7 million monthly downloads, becoming a competitive option among data modeling libraries. The release signifies the production readiness of Polars' in-memory engine and API, positioning it as a top open-source choice for fast data processing. Future plans include redesigning the streaming engine for improved performance and introducing GPU acceleration with NVIDIA RAPIDS for optimal efficiency. Additionally, Polars Cloud is in development to offer a managed service for hosting and scaling Polars. Short-term goals involve enhancing functionality with features like right joins, extended metadata support, and extended SQL support. The project follows a versioning philosophy inspired by Rust's nightly system, ensuring stability and backward compatibility. Polars expresses gratitude to contributors and the community for their support and invites individuals interested in joining the team to explore available roles.

Link Icon 4 comments
By @rcarmo - 4 months
Polars has been my go-to for six months now. The performance gains for what I do are pretty great, and the ability to write out Parquet with minimal hassle is just dandy.

If it weren’t for resume-driven architectures, it would make a great alternative to Spark for high volume bronze-to-silver cleanup and normalization steps.

By @jeffbarg - 4 months
It's interesting that they are explicitly not committing to holding the API constant (which seems quite common & expect for a "1.0"). I generally like that philosophy, but I wonder if it will lead to some unexpected whiplash in the future for people now expecting the core to be stable.
By @jmakov - 4 months
Any examples od how to run it on a GPU?