[issue26571] turtle regression in 3.5

William Navaraj added the comment: Hi all, Sorry. I seem to have stepped on someone's toes or no one likes turtle any more (as this is active since 2016). As you can see, I am new here and still getting a feel for these procedures. I was preparing a Jupyter notebook for my students. I

[issue26571] turtle regression in 3.5

Change by William Navaraj : -- nosy: +williamnavaraj nosy_count: 6.0 -> 7.0 pull_requests: +28569 pull_request: https://github.com/python/cpython/pull/30355 ___ Python tracker

[issue26571] turtle regression in 3.5

Change by Roundup Robot : -- nosy: +python-dev nosy_count: 5.0 -> 6.0 pull_requests: +28547 pull_request: https://github.com/python/cpython/pull/30332 ___ Python tracker ___

[issue26571] turtle regression in 3.5

Change by Irit Katriel : -- versions: +Python 3.10, Python 3.11, Python 3.9 -Python 3.5 ___ Python tracker ___ ___ Python-bugs-list

[issue26571] turtle regression in 3.5

Furkan Onder added the comment: PR has been sent. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue26571] turtle regression in 3.5

Change by Furkan Onder : -- keywords: +patch nosy: +furkanonder nosy_count: 4.0 -> 5.0 pull_requests: +18820 stage: needs patch -> patch review pull_request: https://github.com/python/cpython/pull/19465 ___ Python tracker

[issue26571] turtle regression in 3.5

Change by Carol Willing : -- stage: -> needs patch ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue26571] turtle regression in 3.5

Robert Harder added the comment: Thanks for pointing out the workaround. Was driving me crazy. Possible fix is to add TurtleScreen._RUNNING = True ~line 967 in turtle.py, in TurtleScreen.__init__ function. -- nosy: +Robert Harder ___ Python

[issue26571] turtle regression in 3.5

Ethan Furman added the comment: Serhiy, is this a quick fix you can get in? -- ___ Python tracker ___ ___

[issue26571] turtle regression in 3.5

Ellison Marks added the comment: Just as an update, I've been working around this by manually setting TurtleScreen._RUNNING to True before calling Turtle() again, which produces the desired behaviour in both 3.4 and 3.5. Haven't noticed any bad effects so far. --

[issue26571] turtle regression in 3.5

Changes by Serhiy Storchaka : -- assignee: -> serhiy.storchaka nosy: +serhiy.storchaka ___ Python tracker ___

[issue26571] turtle regression in 3.5

Changes by Ethan Furman : -- nosy: +ethan.furman ___ Python tracker ___ ___

[issue26571] turtle regression in 3.5

New submission from Ellison Marks: 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