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 ned.deily
Recipients Saimadhav.Heblikar, jesstess, ned.deily, python-dev, terry.reedy
Date 2014-05-27.01:27:57
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
"2. Htest's for GrepDialog, outputwindow, configDialog and Filelist are not progressing because of assert statements in"

The asserts are to ensure that none of the Tk-variant tests (isCarbonTk(), isCocoaTk(), et al) are called before _initializeTkVariantTests(root) has been called.  And _initializeTkVariantTests can only be called after the initial calls to Tk have been made to create an initial window environment; it's only at that point that we can call Tk to enquire what variant of Tk we are running under ( and 33).  _initializeTkVariantTests is called from macosxSupport.setupApp which is called from PyShell.main.  This is fine for normal IDLE startup but it doesn't take into account the module level tests.  Ideally, you do want to have run _initializeTkVariantTests before running GUI tests so that the behavior is properly conditioned on Tk variant type, so stubbing out the Tk type with macosxsupport._tk_type = "other' is not desirable.  Perhaps the best way to deal with it is to create a common GUI test initialization function that is called by all of the GUI tests; the initialization function would be responsible for creating the Tk() root, calling _initializeTkVariantTests, and any other common steps that might arise.
Date User Action Args
2014-05-27 01:28:01ned.deilysetrecipients: + ned.deily, terry.reedy, jesstess, python-dev, Saimadhav.Heblikar
2014-05-27 01:28:00ned.deilysetmessageid: <>
2014-05-27 01:28:00ned.deilylinkissue21477 messages
2014-05-27 01:27:58ned.deilycreate