An Introduction to Polars
summary
Compares Pandas and Polars by showing concrete moves: loads a Strava GPX, casts elapsed seconds down to int16 (fails at int8), converts timestamps to Mountain time, and spots a one‑minute flatline that matches the crash — a surprising, actionable result. Demonstrates chaining into a reusable cleaning function, lazy frames that push projection/filtering into the reader, and GPU runs (NVIDIA backend) that yield about 10× speedups; warns that map_elements is ~20× slower than native expressions. Highlights Polars implementation in Rust, Arrow zero-copy, and lazy frames.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 10:25Why Polars vs pandas
- 21:31Loading Strava data
- 30:06Polars code best practices
- 46:20Handling strings dates missing
- 1:08:29Aggregations and visualizations
- 1:17:58Q&A
related talks
58mFrom Pandas to Polars Upgrading Your Data Workflow
28mExpressive & fast dataframes in Python with polars
38mExpressive and fast dataframes in Python with polars
02h 14mGetting Started with Polars
25mIntegrating Rust with Python...
01h 16mPower up your Polars code with Polars extention
22mDon’t Write Polars Code with a Pandas Accent
37mPolars 1.0 and beyond