➜

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 terry.reedy
Recipients Jarrod Petz, eryksun, paul.moore, serhiy.storchaka, steve.dower, terry.reedy, tim.golden, zach.ware
Date 2016-06-11.00:12:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1465603948.52.0.856359768795.issue27263@psf.upfronthosting.co.za>
In-reply-to
Content 
As IDLE maintainer, this annoys me also. IDLE and in particular test_idle necessarily change the environment by calling tkinter.Tk().  When run under test.regrtest, test_idle gets slapped with a warning, and in 3.6, gets labelled a failure, even when it passes.

This issue cuts the other way too.  IDLE works for months and then stops working.  User posts "IDLE stopped working' on Stackoverflow.  In at least some cases, user installed a program that installed ab incompatible tcl/tk and set TCL_LIBRARY (which Python does not).  tk and tkinter get trapped by what for us is a bad setting.

Serhiy, could the _tkinter startup code recover from this and revert to using the one we installed?  Should I open a separate issue?
History
Date User Action Args
2016-06-11 00:12:28terry.reedysetrecipients: + terry.reedy, paul.moore, tim.golden, zach.ware, serhiy.storchaka, eryksun, steve.dower, Jarrod Petz
2016-06-11 00:12:28terry.reedysetmessageid: <1465603948.52.0.856359768795.issue27263@psf.upfronthosting.co.za>
2016-06-11 00:12:28terry.reedylinkissue27263 messages
2016-06-11 00:12:27terry.reedycreate