You don't always need NumPy
summary
Claim: many non-numeric parts of a workflow are faster to build and more robust with standard Python or small focused tools than forcing everything into NumPy. Concrete examples: use lists, dicts, sets, tuples and collections.Counter for bookkeeping; use generators to stream huge CSVs line‑by‑line and avoid GBs of in‑memory data; use SQLite durable transactions for resumable long jobs. For heavy domain needs pick proven C libraries or databases (roaring bitmaps, sortedcontainers, Neo4j, Elasticsearch, PostGIS) rather than inventing array indirections.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 2:55Getting stuck
- 3:57The fun part
- 4:38The friction
- 6:03The practical part
- 6:38Bag of words
- 8:41Inbuilt data structures
- 9:08Lists
- 10:19Sets
- 11:24Dictionaries
- 11:46Tuples
- 12:47Semantics
- 13:28Standard Library
- 15:11Generators
- 17:34Generator
- 19:04Database
- 20:25SQLite
- 21:25Databases
- 22:55Smaller libraries
- 24:00Wrapping up
related talks
26mSmall Big Data: using NumPy and Pandas when your data doesn't fit ...
34mSmall Big Data: using NumPy and Pandas when your data...
37mThe Python Ecosystem for Data Science: A Guided Tour
01mSmall Big Data: using NumPy and Pandas
01h 27mMaking computation easier with cool Numpy tricks
45mPython for Speed, Scale, and Science
29mI wish I learnt that earlier!
43mWhy do I need to know Python- I'm a pandas user
