Peter Wentworth <p.wentwo...@ict.ru.ac.za> added the comment: I can confirm the crash persists as of Python 3.1.3 on Windows, and would like to add my vote to prioritizing it.
Without having delved into the code, it seems strange that the rapid stream of events is causing stack overflow / recursion limit problems. It suggests that tkinter is allowing new event arrivals to interrupt older event handling, so that the older ones remain incomplete as the newer ones pile up on the stack. If this is the case, it is going to lead to long-term instability, and needs attention. The usual technique is to use a queue to decouple "occurs now" from "handle immediately". (The OS puts the mouse and keyboard events onto window's event queue). So the mainloop that services the event queue should not start handling a new queued event until the previous handling has completed. ---------- nosy: +Peter.Wentworth _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue6717> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
