Summary

The typing makes it clear that both are used.

density ofPath.hatch is typed asfloat. This is then passed tohatch.get_path, where it is typed asint and then does:

hatch_type is one of the hatch methods and typically has a line like:

As seen it is possible to pass a float until here.

Proposed fix

I see two solutions:

1. Typedensity ofPath.hatch asint. This makes it consistent and there are no consequences.
2. Typedensity elsewhere asfloat and remove theint(density) inget_path. This will work properly from a typing pespective, but change the appearance. For example, usingPath.hatch("/xX/xX", 1.9) will changenum_lines ofNorthEastHatch from6*int(1.9) = 6 toint(6*1.9) = 11. However, it will also allow a more detailed control of the density in a more natural way.