Issue 22236: Do not use _default_root in Tkinter tests

Currently many Tkinter tests depends on tkinter._default_root. I.e. they reuse the same Tcl interpreter and main window. This can cause unexpected dependencies between tests. Proposed patch creates new root for every test, this makes tests mutually independent. It also fixes some bugs in NoDefaultRoot mode and get rid of 'can't invoke "event" command:' messages in tests. This patch is needed to run Tkinter tests in different "wantobjects" modes (issue21585).

For idle tests, I already avoid the default root and (intend to) create all widgets as a descendent of an explicit root.  This allows explicit deletion and avoidance of error messages and memory leaks. This seems to cover the majority of changes.

An explicit root is mostly true of idle code also, but there seem to be a few exceptions (as indicated by error messages). I presume that deleting and preventing the re-creation of default root, with the code in the patch, would cause a traceback revealing the location of such exceptions. That would have to be done before the offending code is run.

I do not see any need to try to modify the tkinter module for each test function (and slow down tkinter tests). It seems that "tkinter.NoDefaultRoot()" should be moved to destroy_default_root and that function called just once at the top of the module.

Creating and destroying root takes over .04 seconds on my machine.
>>> timeit('root=Tk(); root.destroy()', 'from tkinter import Tk', number=100)
4.222483729329078
Doing it once per test method, with widgets added, will be noticeable.

Unless a test modifies the root widget itself (other than its set of children), I would rename the AbstractTkinterTest methods to setUpClass and tearDownClass, and leave setUp for regeneration of the specific widget or widgets being tested. That is what we do for Idle gui test classes, and only that often because setUpModule and tearDownModule do not work on 2.7. 

-
In one module, you have this change:
 # Make sure tkinter._fix runs to set up the environment
-support.import_fresh_module('tkinter')
+tkinter = support.import_fresh_module('tkinter')

In test/test_idle, I test presence of tkinter with 
  tk = import_module('tkinter')  # imports _tkinter
Perhaps this should use import_fresh_module instead.  Tests seems to work, though there are occasional obscure interaction problems in test suite.

In updated patch the root windows is created only once per test class.

New changeset 32fdaf401e50 by Serhiy Storchaka in branch '2.7':
Issue #22236: Tkinter tests now don't reuse default root window.  New root
http://hg.python.org/cpython/rev/32fdaf401e50

New changeset dd1dffe6f0d2 by Serhiy Storchaka in branch '3.4':
Issue #22236: Tkinter tests now don't reuse default root window.  New root
http://hg.python.org/cpython/rev/dd1dffe6f0d2

New changeset 014060738f7f by Serhiy Storchaka in branch 'default':
Issue #22236: Tkinter tests now don't reuse default root window.  New root
http://hg.python.org/cpython/rev/014060738f7f

Thanks Terry and Zachary for your reviews. I have committed the patch in haste because other issues depend on it.

See Issue22770 for details of a potential Tk crash that can occur on OS X when running tests as a result of these changes and for a workaround.

assignee: serhiy.storchaka
resolution: fixed
stage: patch review -> resolved

messages: + msg225612