As we add more features to the turtle support, it gets more annoying to keep the MockTurtle class in synch with SvgTurtle. It was nice to have it in a single file with no dependencies, but it's probably time to make it a subclass of MockTurtle. Put it in an optional feature of the package, so users don't have to install the svgwrite dependency unless they want it.
Alternatively, could we simplify both MockTurtle and SvgTurtle by making them subclasses of Turtle or RawTurtle? Would it be easier to mock out all the dependencies on tkinter than it is to duplicate the features that Turtle builds on top of TNavigator?
As we add more features to the turtle support, it gets more annoying to keep the
MockTurtleclass in synch withSvgTurtle. It was nice to have it in a single file with no dependencies, but it's probably time to make it a subclass ofMockTurtle. Put it in an optional feature of the package, so users don't have to install thesvgwritedependency unless they want it.Alternatively, could we simplify both
MockTurtleandSvgTurtleby making them subclasses ofTurtleorRawTurtle? Would it be easier to mock out all the dependencies ontkinterthan it is to duplicate the features thatTurtlebuilds on top ofTNavigator?