Ned Deily <n...@python.org> added the comment:
Sorry, there isn't a particular rush to close issues as some of them stay open for years. And that's not good for anyone. "resolved" on the issue tracking does not necessarily mean a problem is resolved to everyone's satisfaction, it just means that it is no longer active in our backlog (which currently numbers over 6000). I don't claim to be a turtle expert but the bit of time I spent looking into this issue and my years of triaging Python issues lead me to conclude this is almost certainly a problem with your program and not with Python itself. We could leave it open but the chances that any other core developer would spend time looking further at it are slim. That's why I suggested asking on user forums where you are much more likely to get useful and more rapid feedback. And as I earlier suggested, if it *does* turn out to be a demonstrable problem with turtle or elsewhere in Python, you can easily reopen the issue and we can go from there. I hope that makes some sense! ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue35211> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
