Why is there a HexSingleGrid(HexGrid) and a HexGrid?

[jackiekazil]

Why is the HexSingleGrid subclassed from HexGrid and HexGrid has nothing in it?
I was reading through the code and confused by this -- because it is also visible in the docs. Wondering if there was logical reason or if someone remembered why? I was thinking we should get rid of HexGrid or make it private.

See the following two lines -

mesa/mesa/space.py

Line 742 in b2f642f

class HexSingleGrid(_HexGrid, SingleGrid):

mesa/mesa/space.py

Line 768 in b2f642f

class HexGrid(HexSingleGrid):

[rht]

It wasn't made private in order to maintain backward compatibility, but should have been made private during the 2.0 release.

[jackiekazil]

Thank you. Where do you think is the best place for marking that as something for 3.0?
Who knows when 3.0 happens... but I want to make sure that doesn't get forgotten about.

[rht]

We could open an issue that is set as a blocker for 3.0 milestone.

[jackiekazil]

#1847