☰Read-only archive⌕
Looking for help with Bokeh?

This is a read-only archive. Ask questions and join the conversation on GitHub.

Visit Community Support on GitHub →
Archived discussions · Captured October 28, 2026

Is "setv" less performant?

Community Support
roinr
roinr

I’ve created a custom select widget and I’m using the setv method for updating model’s properties.
Recently I found out that when there’s a large amount of options in the dropdown, the widget gets stuck after selecting a few options (right at the point where the value property should get updated).
After going through Bokeh’s built-in widget definitions I noticed that usually a regular assignment is used instead of using setv. What’s the difference between the two? Is setv known for a tendency to be less performant in some cases?

⌁   Link to post
Bryan
Bryan

setv is a lower-level implementation detail. There is never any reason to use it unless you need to pass one of the specialized options e.g. {silent: true} to it, but this is rare/unusual, even in the BokehJS codebase itself.

⌁   Link to post

End of archived discussion · Replies are disabled