Axis tick labels do not work with integer float locations

[SvenWarnke]

If ticks are set with location and label, label is not used if location is a float that could be converted to integer.
Example:
import holoviews as hv
hv.extension('bokeh')
hv.Curve([(1, 2), (2, 2)]).options(yticks=[(1.3434, 'hi'), (2., 'ho')])
yields

whereas it is correctly displayed for integer position:
hv.Curve([(1, 2), (2, 2)]).options(yticks=[(1.3434, 'hi'), (2, 'ho')])

The same holds for xticks.

I have holoviews 1.11.3

[philippjfr]

That's bizarre, thanks for reporting this. I'm guessing this is an upstream issue in bokeh but will have to confirm.

[philippjfr]

Yeah, pretty sure this is a bokeh issue, specifically because the ticks are specified as a dictionary, and in JS objects can only have string keys. Since the string representation of 2.0 in JS is "2" the lookup fails, because in Python the representation is "2.0".

[philippjfr]

I'll work around this by casting floats that are ints to integers, but this should probably be fixed in bokeh as well.

[Sieboldianus]

Edited: I will add a new issue and reproducible example for my problem.

[MarcSkovMadsen]

Hi @Sieboldianus . Thanks for reporting. Please open a new issue. This one has been closed.

And please include a minimum, reproducible example that can run end to end. It will make it much easier for the volunteers and contributors that contribute in their limited spare time to understand, reproduce and fix. Thanks.

[Sieboldianus]

Yes, thank you. Already working on a minimum, reproducible example. Apologies for that.

[MarcSkovMadsen]

No problem. I'm just nudging here so that we can get the Philipp and his gang to focus their energy on fixing the issue instead of understanding, reproducing, making test examples etc. :-)

And again thanks for taking the time to contribute to making HoloViz better for all of us. A well described new issue is a "gift" to a project 👍

ps. screenshots and gifs make it even more clear what the issue is :-)

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.