This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Ellison Marks
Recipients Ellison Marks
Date 2016-03-16.04:59:14
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I noticed some odd behaviour when running some turtle code I wrote using python 3.5. A simplified example:

>>> from turtle import Turtle
>>> t = Turtle()
>>> t.getscreen().bye() # or manually close the turtle window
>>> t2 = Turtle()
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/lib64/python3.5/", line 3816, in __init__
  File "/usr/lib64/python3.5/", line 2557, in __init__
  File "/usr/lib64/python3.5/", line 2660, in _update
  File "/usr/lib64/python3.5/", line 2646, in _update_data
  File "/usr/lib64/python3.5/", line 1292, in _incrementudc
    raise Terminator

This code works under 3.4, opening a new turtle window the second time Turtle() is called. Under 3.5, a blank white window opens.

This seems to be related to, as the only point that raises Terminator is guarded by a check for `if not TurtleScreen._RUNNING:`
Date User Action Args
2016-03-16 04:59:15Ellison Markssetrecipients: + Ellison Marks
2016-03-16 04:59:15Ellison Markssetmessageid: <>
2016-03-16 04:59:15Ellison Markslinkissue26571 messages
2016-03-16 04:59:14Ellison Markscreate