~/talk

The PyData map: Presenting a map of the landscape of PyData tools

Talkat PyData Amsterdam 2016 · 2016-03-12..03-13· [python, developer-experience]
slides:none on file

A practical map of the PyData landscape that names tools and shows where each actually helps: pure Python and toolz for small fast work, NumPy/Pandas for in‑memory analysis, Blaze to write expressions then execute them on Postgres or other back ends, bcolz compresses 1GB to 51MB (~7×) in a ctable, Dask handles medium data (examples: ~342k UK/Ireland schools found; come into play ≈16GB+), Spark for massive distributed workloads. 1GB→51MB bcolz (≈7×) Dask finds ~342k schools; medium data >RAM (≈16GB) Blaze: write expression, execute on Postgres

AI-written summary · about

  1. 0:00PyData landscape intro
  2. 1:50Why Python for analytics
  3. 3:56NumPy and pandas updates
  4. 4:37Python 2.6 data problem
  5. 6:43Functional programming with PyTools
  6. 7:47Pandas and NumPy roles
  7. 8:31XArray for labeled data
  8. 9:37Blaze decoupling expressions
  9. 10:40Dask for parallel computing
  10. 13:27Bcolz fast storage
  11. 15:55Quantopian’s Bcolz case
  12. 17:39Dask arrays for big data
  13. 19:26When to use Dask
  14. 20:50Speeding up Python with Numba
  15. 21:55Python big data with Dask
  16. 23:42Arrow for data formats
  17. 25:06Ibis SQL-like analytics
  18. 26:31Using the PyData map
  19. 27:56Stats and ML in PyData
  20. 28:58Statsmodels and scikit-learn
  21. 29:41Future of PyData tools
  22. 30:22Call to action
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.