"Jeff Hobbs" <jeffh@ActiveState.com> writes: > Ah yes, a few instances like that can be considered incompatible, but > it was really a correction for buggy behavior that existed in Tk. Unfortunately, for Python, this was more than just a few instances. If Tkinter receives an event, it would convert all fields wholesale, regardless of whether they would be needed or not. That means that any Tkinter application using Tk bind would crash - even if it did not look at the event at all. There were ten or so bug reports about it, both on SF and comp.lang.python. Now, I understand the reason for the change, and I agree it is a sensible change. It also is a serious incompatibility. I have no problems with serious incompatibilities as long as they are properly documented and announced. Regards, Martin
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4