Philipp Rudiger

>So then I'd amend my question: what is the reason we cannot use ipywidget comms internally automatically, and avoid users having to use or know about BokehWidget? (BokehModel ?) Good...

Thanks, that's a good point. Personally I don't think this was intentional but I appreciate that it's a significant change in behavior. For mutable objects the correct way to trigger...

As an example to illustrate this point, the two mutables that we do have equality comparisons defined for (list and dict) do not trigger an event: ```python import param class...

The docs about trigger also make this point: >Usually, a Watcher will be invoked only when a parameter is set (and only if it is changed, by default). What if...

Definitely agree, `on_init` should be independent from watching for changes.

> My first instinct is 1 and 10, but I don't mind it being wontfix, as long as the default is None (right now it's 0 if I recall). In...

Thanks for the detailed writeups both of you. I fully agree with @maximlt's summary and agree that making `check_on_set` be an explicit setting is fine but `allow_None` would be far...

Not sure I have anything good. In the Panel context this will line up with Autocomplete and MultiChoice widgets which allow either restricting the options or adding new options. There...

Agreed, my vote is to take no action on renaming `check_on_set` or any major reworking of `_update_state` for the 2.0 release.

No my misunderstanding, that all sounds fine. In the end _update_state is just an implementation detail though so no opinion whether to remove it, if it gets eliminated by making...