When we request npartitions=2 when converting a pandas to a daskDataFrame, we may receive 1 or 2 partitions depending on the version of dask. Line and area tests using axis=0 have different results depending on the number of partitions as datashader does not cope with npartitions > 1 for these axis=0 situations.
The workaround here is to check the number of partitions in the returned dask.DataFrame to do an appropriate comparison test so that our CI passes regardless of dask version. Our functionality is no more broken than it was before, but users are more likely to be seeing inappropriate results with dask >= 2022.8.
This is a workaround for issue #1106.
When we request
npartitions=2when converting apandasto adaskDataFrame, we may receive 1 or 2 partitions depending on the version ofdask. Line and area tests usingaxis=0have different results depending on the number of partitions asdatashaderdoes not cope withnpartitions > 1for theseaxis=0situations.The workaround here is to check the number of partitions in the returned
dask.DataFrameto do an appropriate comparison test so that our CI passes regardless ofdaskversion. Our functionality is no more broken than it was before, but users are more likely to be seeing inappropriate results withdask >= 2022.8.