Summary

The typing makes it clear that both are used.

density of Path.hatch is typed as float. This is then passed to hatch.get_path, where it is typed as int 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. Type density of Path.hatch as int. This makes it consistent and there are no consequences.
2. Type density elsewhere as float and remove the int(density) in get_path. This will work properly from a typing pespective, but change the appearance. For example, using Path.hatch("/xX/xX", 1.9) will change num_lines of NorthEastHatch from 6*int(1.9) = 6 to int(6*1.9) = 11. However, it will also allow a more detailed control of the density in a more natural way.