Hi @jonathansailing, for proposing features, a GitHub development discussion is a good place (but here is also fine).
From experience “properties that depend on other properties” are a huge PITA. If Bokeh was just a pure-Python tool, I might be inclined to consider these cases more. But having to worry about cross-runtime synchronization just opens too many questions and headaches. Basically is step and num_step are both independently user-settable, there are suddenly lots questions about how to enforce that that two properties stay consistent with respect to each other (and do those enforcements trigger their own cascading property updates or not?) And how to detect problem situations and warn about them (across runtime-boundaries). I can imagine this would need dozens of tests to maintain, and not the easy basic pure-Python unit tests, either, since BokehJS is in play.
And at the end of the day, all that work would be just to avoid this line:
slider.step = (slider.stop - slider.start) / N
Speaking plainly, I think it is unlikely that we would pursue this.