-
-
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
ValueError with {+framewise} #1681
Comments
Easy fix, assigning to 1.8.1. |
@jlstevens Actually this needs some discussion. The problem here is that this code uses the |
Unless you can think of a particular use-case, I don't see an issue with disallowing None as values. Containers such as HoloMaps expect the values to be HoloViews elements/objects and not None as it is afaik. |
I cannot.
Right all our concrete containers do, but some of the baseclasses, e.g. Tree and NdMapping don't have such restrictions at present afaik. |
None values as tree values don't seem particularly desirable and I don't have an issue with disallowing None values in NdMapping either. Right now I think fixing this issue takes priority over supporting None values. |
Good, I was just playing devils advocate. My preference is also to make this fix now. |
This should be fixed now and will land in the 1.8.1 release scheduled for tomorrow, please reopen if you encounter any issues. |
works fine without {+framewise} but produces the following error with it:
The text was updated successfully, but these errors were encountered: