gh-135272: Activate doctests on turtle module #138877
Draft
+206
−36
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is a WIP to fix #135272
I'd like reviews and comments before I continue.
Also, I need some help:
I added a
load_tests
function to include doctests in unittest, and already fixed some ERRORs on tests (8 remaining), the majority were just addingimport turtle
and instantiating aturtle
object. Is it possible to avoid repeating it in every doctest?I mocked the
mainloop
function. But maybe it was the right way. How is it?Any recommendations about how to mock other functions that wait for a user action (num/textinput, ...)?
The
optionflags=doctest.ELLIPSIS|doctest.NORMALIZE_WHITESPACE,
options seem not to work properly. For instance,(0,0)
is saw different of(0, 0)
(common on tests with position()). (Or I did understand how these options work.This PR is related to #111704