Replies: 1 comment 1 reply
-
Thanks for raising a discussion item @orf!
Generally speaking software environment mismatches are one of, if not the, most common pain point Dask users run into. However, you bring up a fair point that minor differences in Python are usually okay. That said, there are some commonly used libraries that don't provide the same compatibility guarantees
Users don't always check scheduler logs and, given how problematic software version mismatches can be, I think there's value in emitting warnings directly in the user's
Do you have any suggestions on how the warning message could be improved? For example, we could add an additional note here around how often differences in Python versions are problematic. |
Beta Was this translation helpful? Give feedback.
-
Dask added minor version mismatch warnings in dask/distributed#595.
I see value in providing this feature, but do we really need to display such a large warning if minor Python versions are mismatched? The Bytecode is explicitly marked as stable between bugfix releases and Pickle is also marked with the same stability guarantees.
While rolling out Dask in our company this was a big source of confusion. The error message isn't particularly helpful, and distributions like Debian package Python
3.9.2
rather than the current latest3.9.7
which makes minor mismatches quite common.I guess the question is: Are minor mismatches currently such a huge problem that we should frequently display a very large table warning? Maybe a smaller warning on the scheduler only might suffice?
Beta Was this translation helpful? Give feedback.
All reactions