question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Setting `tools` option does not work with Bokeh

See original GitHub issue

Hi, Setting tools as a curve-option does not work with v1.13.4 and Bokeh v.2.2.1. However, setting default_tools does do the trick. Also, both these settings have the exact same description in hv.help(hv.Curve).

This also affects the first example in this documentation page (under “Core concepts”) where the only apparent tools should be "hover".

I suspect it’s like this for a few versions now (since I remember that I used default_tools a few months ago), but still… So either fix the docs, or, better yet, merge these attributes into a single attribute to avoid confusion.

Issue Analytics

  • State:open
  • Created 3 years ago
  • Comments:11 (7 by maintainers)

github_iconTop GitHub Comments

2reactions
jlstevenscommented, Sep 30, 2020

The suggestion of tools=[..., "hover"] is perhaps the most outlandish abuse of Ellipsis I have ever seen. 😃

I also agree that the parameter docstrings should be checked and updated to be as clear as possible.

2reactions
jbednarcommented, Sep 29, 2020

both these settings have the exact same description in hv.help(hv.Curve)

If that’s true, it should be fixed! Both those options should specifically mention the other one and make it clear how they relate, which is that tools adds additional tools to whatever is in default_tools, and default_tools overwrites the entire starting list of tools.

But I don’t see anything else that should be done; having to list the existing tools explicitly would be very painful, and we can’t change the meaning of tools because that would break backwards compatibility, which would cause at least as much trouble as it solved.

If we didn’t have to worry about backwards compatibility or Python 2, we could imagine supporting some shorthand like tools=[..., "hover"] (where ... would be replaced by HoloViews with the existing tools), but I think that ship has sailed.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Configuring plot tools — Bokeh 2.4.3 Documentation
This way of adding tools works with any Bokeh Plot or Plot subclass, such as Figure . ... This method does not allow...
Read more >
Trouble displaying Bokeh toolbar - Stack Overflow
The only problem is that im not getting the "Bokeh tool bar" next to my graph. My code looks like this from flask...
Read more >
Applying Customizations — HoloViews v1.15.3
When customizing a single element, the use of an option builder is not ... To illustrate how settings are kept separate, let us...
Read more >
Interactive Data Visualization with Bokeh - Trenton McKinney
Create a figure p using the figure() function with x_axis_type set to 'datetime' . The other two parameters are x_axis_label and y_axis_label ....
Read more >
Custom build steps / Moving Bokeh off setup.py
So what are our options here? Looking at build it does not seem sufficient to support a customization like this. Are there other...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found