[issue17803] Calling Tkinter.Tk() with a baseName keyword argument throws UnboundLocalError

2013-08-22 Thread Serhiy Storchaka
Serhiy Storchaka added the comment: Fixed in changesets fa82071bb7e1 and 0f17aed78168. -- nosy: +serhiy.storchaka resolution: - duplicate stage: test needed - committed/rejected status: open - closed superseder: - Security bug in tkinter allows for untrusted, arbitrary code

[issue17803] Calling Tkinter.Tk() with a baseName keyword argument throws UnboundLocalError

2013-04-26 Thread Terry J. Reedy
Terry J. Reedy added the comment: Line 35 is import sys so sys imports within functions are superfluous, as well as contrary to current guidelines. There is another on 1033. Both were removed before 3.3, so this amounts to a 2.7 backport. It took me a moment to see that the unneeded

[issue17803] Calling Tkinter.Tk() with a baseName keyword argument throws UnboundLocalError

2013-04-20 Thread Yasuhiro Fujii
New submission from Yasuhiro Fujii: Calling Tkinter.Tk() with baseName keyword argument throws UnboundLocalError on Python 2.7.4. A process to reproduce the bug: import Tkinter Tkinter.Tk(baseName=test) Traceback (most recent call last): File stdin, line 1, in module File

[issue17803] Calling Tkinter.Tk() with a baseName keyword argument throws UnboundLocalError

2013-04-20 Thread R. David Murray
R. David Murray added the comment: Thanks for the report and patch. It would be nice to turn that test into a unit test. I've run the test on 3.4; this appears to be a 2.7 only bug. -- nosy: +r.david.murray stage: - test needed ___ Python tracker