'RuntimeWarning: divide by zero encountered in scalar divide' causing Axes rendering failure for axis values 0 about manim HOT 3 CLOSED

The case of passing a "0-lengthx or y range toAxes` is somewhat odd, I am not sure it is worth to investigate how a clean solution for it can be implemented.

Can we just raise an exception in the __init__, so that there is a better error message? Something like

x0, x, dx = x_range
if 0 in (dx, x0+x):
    raise ValueError("Axes does not handle x_range's of 0, maybe you wanted to use NumberLine instead?")

from manim.

Hmm, Axes is by default a two-dimensional coordinate system. If you just want one dimension, you should use a NumberLine instead.

The case of passing a "0-lengthx or y range toAxes` is somewhat odd, I am not sure it is worth to investigate how a clean solution for it can be implemented.

from manim.

Hmm, Axes is by default a two-dimensional coordinate system. If you just want one dimension, you should use a NumberLine instead.

The case of passing a "0-lengthx or y range toAxes` is somewhat odd, I am not sure it is worth to investigate how a clean solution for it can be implemented.

Thanks for the suggestion @behackl , will be reading further on this as I have just started using the tool and was for sure not aware of the clean way of doing it. Reading the exception message felt that it will be good to report the edge case.

Can think of a scenario where the axes values are dynamically calculated based on some logic and are used to define Axes mobject. it's possible to hit this exception again if the values come out to be 0 at runtime

from manim.