Release of Polars 2.0

(pola.rs)

71 points | by simicd 1 hour ago

5 comments

  • gozzoo 21 minutes ago
    I'm not following the trends closely, but has Polars become a full replacement for Pandas? Are there use cases where one is better suited than the other?
    • 392 8 minutes ago
      my understanding is Polars is faster, scales better without using external solutions, better API, +Rust. Pandas wins if you want to use what the vast majority of folks are using and have used in the past. Probably has a more complete set of helpers / recipes for the little things you bump into when using it thoroughly, but in the age of LLMs, I think that's minor.
  • sgarland 28 minutes ago
    TIL that Polars supports SQL. Amazing.
  • hnd9q09qk4 30 minutes ago
    Thing I care about most is whether the old eager-vs-lazy footguns got cleaned up. Half my bugs were a stray collect() in a loop killing the query plan.
  • dkgs 39 minutes ago
    A coincidence with the fact duckdb is supposed to release 2.0.0 very soon? :)
    • orlp 29 minutes ago
      Actually yes. We had already been planning to do 2.0 for a long time. We originally said we'd move on from 1.x quickly when released 1.0 but ended up staying at 1.x much longer than intended.

      From a quick check our first PRs were merged to the 2.0 branch in June:

          2026-06-17T21:27:51Z #27993 chore: Stop coercing `pl.col(...)` to selector ...
          2026-06-18T14:19:26Z #27996 chore!: Replace multi-seed hash API with a single seed
          2026-06-19T07:05:11Z #27991 chore(python!): Remove `Expr.flatten` function
    • m00dy 29 minutes ago
      Are they competing for something?
      • vindex10 7 minutes ago
        > first class SQL support, which together with the performance improvements has Polars leading DataFusion and DuckDB in TPC-H and TPC-DS1 benchmarks,

        Apparently about something ))

  • tonyhart7 21 minutes ago
    finally long time coming

    cant wait to upgrade my Quant trading bot