Closed sdc50 closed 5 years ago
Agreed. This sounds like a bug.
I noticed that yesterday as well, but hadn't gotten around to filing a bug report. Thanks for doing it for me!
yes! I ran across that a while back but I thought I just misunderstood what it was supposed to do. Always better to file a report I suppose.
My best guess is that parambokeh (or its future replacements) will never support the next_n
option because the JS code that paramnb uses to make it work is exceptionally hacky.
We should definitely make it not accept the option, then! :-) In any case I think the recent Panel work will make it very unlikely that next_n would really be the best choice in any scenario.
Agreed, another problem with it is that even in paramnb it doesn't work in JupyterLab.
I also vote against next_n
support due to how hacky it is to get working...
Specifying the
next_n
argument when callingparambokeh.Widgets
has no effect.I would expect this to run the next cell when a parameter widget is updated but nothing happens.