GeezerVison

Fully implemented and tested a teleport method as described by the issue. This method behaves differently from the goto (or setpos) method, and can be especially helpful when creating and filling multiple separate objects.

Implementation:

There already exists a goto method, aliased as setpos | setposition | goto. It basically moves the turtle to the given position, but if the pen is down, it draws a line along the path. Additionally, the move is not instant, and you can see it go along the path to get to the destination. Users of the library may find themselves raising the pen, calling the method, and then lowering it so that a line doesn’t get drawn. Another issue with using goto for this is that regardless of whether the pen is raised, an "imaginary" line is still drawn from the current position to the destination. When filling is enabled, this invisible line acts as a boundary for the fill color. If one were creating multiple separate objects with filling enabled, they would need to run the exact code in the teleport method in order to fill them separately as desired. The following is a demo of the difference between goto and teleport for filling multiple objects.

Justification:

One might think we should just update the goto method to behave this way with a flag like teleport=True. However, all of the pen controlling methods are in one class, TPen, and all of the visual and position controlling methods are in another, TNavigator. The primary turtle class, RawTurtle(TPen, TNavigator) inherits methods from both of these, and since teleport needs access to methods and attributes in both of these classes, this is where it should be written. While it would be possible to give goto access to the TPen class via inheritance, this would be a messy refactor for what should be a distinct method.

Resolves #88773

• Issue: Teleport method for turtle class #88773