This doesn't do it for me: the GUI window still sticks around with this chirpy message until all doctests have finished for all stdlib modules, long after the doctests for turtle specifically have finished:

This doesn't do it for me: the GUI window still sticks around with this chirpy message until all doctests have finished for all stdlib modules, long after the doctests for turtle specifically have finished:

Could you try again?

It works perfectly for me.

Which platforms are we all testing on? I had completely forgotten about this, but would have been on Linux.

I was testing on Windows, Alex's screenshot (above) looks like macOS.

Which platforms are we all testing on? I had completely forgotten about this, but would have been on Linux.

I'm on Ubuntu.

Maybe Alex (or someone on a macOS) could run:

>>> import turtle
>>> turtle.forward(100)
>>> turtle.bye()

I've asked a friend of mine to do this. In his case, the turtle window is gone. However, the Tk process was kept alive. He said that it is a macOS feature. And it is also different from Alex's case.

Two out of three isn't bad :). I wonder about going ahead with this since it will improve things for anyone on Windows or Linux, and if anyone can come up with a fix that works on macOS it can of course be patched in later.

Skimming through the turtle.py code, the only macOS-specific bit is an attempt to raise the window to the top so it doesn't get hidden behind the terminal, which I imagine shouldn't have an impact here. That leads me to believe that this may be a Tkinter and/or Tcl/Tk bug¹, but I don't have the resources to investigate it right now.

Two out of three isn't bad :). I wonder about going ahead with this since it will improve things for anyone on Windows or Linux, and if anyone can come up with a fix that works on macOS it can of course be patched in later.

from memory, I don't think this made the situation any worse for me, so if it improves the situation on other platforms please go ahead!