Terry J. Reedy added the comment: I prepared and tested two slightly different patches for 3.5 and 3.6. I committed the 3.6 patch, then the 3.5 patch, and prepared a null merge (in default), but did not hit the commit button before pushing. I just finished the null merge, creating two heads (in default), which I merged (after updating to Martin's head) and pushed both. Everything looks good here after re-pulling. One of you could recheck in your clones. ---
turtledemo.__main__ creates a framework for running any of the demo files in the package. There is no test_turtledemo unittest. The test is to run it, either with python -m turtledemo in the console or Help => Turtle Demo in IDLE. Two summers ago, before adding the IDLE menu item, I loaded and ran each of the demos, patched a few, as well as .__main__, and re-ran, more than once. For this issue, I only needed to load one demo with the IDLE Dark theme, or a custom version thereof, as the current theme. If someone has not customized the theme selection in IDLE, the default IDLE Classic, black on white, will be used. Testing this issue also required running IDLE and loading a file to be sure the the revised editor still worked, and loading and running the colorizer file, to run its htest (which previously had the same problem as turtledemo). ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue27117> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
