In the Python version of asciichart, the position of the first tick mark
is sometimes drawn incorrectly due to a rounding error. The value should
be round up, but the int function is used instead.
Before the change (the tick mark on the y-axis is at 4.5, but it
should be at 6.25):
Coverage remained the same at 100.0% when pulling 42951af60aacec52ca630250bd0bf054709f0fb2 on pkazmier:fix-position into f3d8b0708c21164c7b7785d96d0774e3f4ea0f9a on kroitor:master.
In the Python version of asciichart, the position of the first tick mark is sometimes drawn incorrectly due to a rounding error. The value should be
round
up, but theint
function is used instead.Before the change (the tick mark on the y-axis is at 4.5, but it should be at 6.25):
After the change:
Note: this bug is not in the node version.