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 LionKimbro
Recipients Emmanuel.Decitre, LionKimbro, Peter.Wentworth, asvetlov, dino.viehland, flupke, gregorlingl, kbk, loewis, pitrou, python-dev, r.david.murray, serhiy.storchaka, terry.reedy, vstinner, willingc
Date 2018-10-27.21:58:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1540677492.06.0.788709270274.issue6717@psf.upfronthosting.co.za>
In-reply-to
Content
I confirm that dragbug.py (2009-08-17!) is failing for me, almost ten years later.  I'm using Python 3.6.1/win32 on Windows 10.

This is really disappointing, because I have students who I'm teaching Python to via turtle, and I like to show them Python working.

I have found a workaround which -- if this bug won't be fixed -- I propose mentioning in the documentation.

The work-around is something like this:

g = {"X": 0, "Y": 0}

def goto_later(x, y): g["X"] = x; g["Y"] = y

def ontick():
    goto(g["X"], g["Y"])
    ontimer(ontick, 10)

ondrag(goto_later)
ontimer(ontick, 10)

That way, there is no opening for recursion within the handler for the ondrag event.
History
Date User Action Args
2018-10-27 21:58:12LionKimbrosetrecipients: + LionKimbro, loewis, terry.reedy, kbk, pitrou, vstinner, gregorlingl, dino.viehland, r.david.murray, asvetlov, flupke, python-dev, Peter.Wentworth, Emmanuel.Decitre, serhiy.storchaka, willingc
2018-10-27 21:58:12LionKimbrosetmessageid: <1540677492.06.0.788709270274.issue6717@psf.upfronthosting.co.za>
2018-10-27 21:58:12LionKimbrolinkissue6717 messages
2018-10-27 21:58:11LionKimbrocreate