-
-
Notifications
You must be signed in to change notification settings - Fork 402
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incompatibility with Datashader.by #4420
Comments
Thanks for the heads up! I've got various fixes for |
@jbednar Actually I was using Datashader installed through |
Ah, ok. I made a slight update to the
|
Looks like holoviews will need some updates, but it would be nice to have those worked out before we release Datashader, in case Datashader also needs updates. |
Fixed in #4438 |
Thanks, @philippjfr ! It came just in time for me. So do I just |
I'll have a build up on the pyviz/label/dev conda channel later today but you can install straight from git as well if you need it asap. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
The exciting development of “by” reduction operator of Datashader is not supported as a valid argument to “aggregator” of the HoloViews.datashade. The main issue seems to be about the member “column” enforced in HoloViews.datashade, whereas Datashader.by only has member "columns". It is desirable to incorporate "by" into the workflow of HoloViews.
ALL software version info
HoloViews version : 1.13.2
Datashader version : 0.11.0a4
Description of expected behavior and the observed behavior
Expected to produce plots when called with Datashader.by. Observed to give errors on member "column" not found on Datashader.by objects.
Complete, minimal, self-contained example code that reproduces the issue
Stack traceback and/or browser JavaScript console output
The text was updated successfully, but these errors were encountered: