Julia Signell

Slides for @dask_dev Workshop at @foss4gna: docs.google.com/presentation/d… There are 3 total slides because I am leaning heavily on the awesome work that folks have done on the @Project_Pythia cookbook ✨✨

Feeling reenergized after sprinting with these @dask_dev folks 🤓 Another amazing @SciPyConf!!

Thanks so much to @DataUmbrella for inviting me to speak! I had a lot of fun playing with bird migration data and getting back in to HoloViz - it's come a long way in the last few years!

@Israsthoughts @dask_dev Dask supports Python 3.8 and 3.9. There are several methods (like .head()) that compute eagerly on dask. Those methods might seem slow if you expect purely lazy outputs. As always, if you are seeing unexpected behavior please report it on GitHub!

@dask_dev @JSignell Hi. Does this mean that dask isn't supported for Python 3.9? I've been having lots of issues regarding EXTREMELY slow processing on simple functions like .head() of a dask datagrams.

The Dask team is happy to announce the release of 2022.02.1 today! #v2022-02-1" target="_blank" rel="nofollow noopener">docs.dask.org/en/stable/chan… Some highlights 🧵:

I just learned about the %history magic in ipython. You can specify the cell number (or range of cells) that you want to print.

Thanks @PyDataDC for inviting me to talk! Slides: github.com/jsignell/insid…

@jcristharif @choldgraf Only the spiders know.

Slides for @dask_dev 2021 updates from @SciPyConf #slide=id.p" target="_blank" rel="nofollow noopener">docs.google.com/presentation/d…

This was so fun! Thanks for having me @pythonbytes

I just learned about `pytest --last-failed` and now I'm obsessed.

@alex_rybchuk @dask_dev @ChelleGentemann haha I forgot about that one :)

@JSignell @dask_dev @ChelleGentemann Shortly followed by "I am an expert node killer"

Favorite quote from the @dask_dev summit: Q: What was your initial experience using Dask and Python A: Lightness and joy @ChelleGentemann

Watching the Dask Summit keynote by Travis and Peter, and "We shouldn't fork the ecosystem" sounds like a quote from The Good Place.

There's still an hour left in the Hacking Dask Tutorial at the Distributed Dask Summit in case you just wanted to learn about schedulers! @__jrbourbeau__ is live now!

Pumped to be presenting the Hacking Dask Tutorial tomorrow with @__jrbourbeau__ at the Dask Distributed Summit!! PSA - don't forget to register (it's super easy...I just did it 🤓)

The Dask Summit is right around the corner! summit.dask.org/schedule/

@_JacobTomlinson Yeah I'm guessing that'd be more annoying than just installing pre-commit.

@JSignell I guess you could have a bot that pushes extra commits onto a branch to fix linting if it fails. Maybe multiple times as a PR is worked on. The user may be a little confused about why they have to pull before they can add more commits themselves though.

Checking linting and formatting as part of your CI adds friction, especially for first-time contributors. Lately I've been thinking it would be better to have a bot that fixes linting in a follow-up PR instead which gets auto-merged on passing tests. What do you think?

A whole other week! Wowowow what won't you come up with?!?! 😀😀😀

Get excited for the dask summit this May!!! summit.dask.org