Ned Deily added the comment: tkinter is pretty much just a thin wrapper around the Tcl/Tk C API so suspicion for behavior like this start there. Usually, the easiest way to confirm that is to write an equivalent test in Tcl using its wish shell but, in this case, there's an even easier way. The memory leak is easy to see if you use the badly out-of-date and seriously flawed system Tcl/Tk 8.5.x supplied by Apple in OS X releases since 10.6. If tkinter is linked with an up-to-date Tcl/Tk, the leak should go away. At least that's the case when using python3.5 from python.org 10.6+ installers and with ActiveTcl 8.5.18 installed. See https://www.python.org/download/mac/tcltk/ for more info.
---------- resolution: -> third party stage: -> resolved status: open -> closed versions: -Python 3.3, Python 3.4 _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue27529> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
