[issue4792] PythonCmd in Modules/_tkinter.c should use the given "interp" parameter

Guilherme Polo added the comment: Merges: r70220, r70221, r70222 -- resolution: -> fixed status: open -> closed ___ Python tracker ___ __

[issue4792] PythonCmd in Modules/_tkinter.c should use the given "interp" parameter

Guilherme Polo added the comment: Fixed in r70219. ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.or

[issue4792] PythonCmd in Modules/_tkinter.c should use the given "interp" parameter

Guilherme Polo added the comment: I will be committing this but I'm afraid a test won't be added for it. Several people told me that creating multiple tcl interpreters (even if only one is active at some point) is problematic, specially in older tcl versions. So if someone can find another way

[issue4792] PythonCmd in Modules/_tkinter.c should use the given "interp" parameter

Guilherme Polo added the comment: Another way to reproduce it (tested using debug build): Python 2.7a0 (trunk:69375:69376M, Feb 6 2009, 20:27:09) [GCC 4.3.2] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import Tkinter >>> Tkinter.Tk() >>> Tkinter.Tk()

[issue4792] PythonCmd in Modules/_tkinter.c should use the given "interp" parameter

New submission from Guilherme Polo : Right now PythonCmd is using the Tcl interpreter stored in self->interp, but this is unsafe and since it is a Tcl_CmdProc it already receives the Tcl interpreter as a parameter. Using the interpreter in self->interp is unsafe because Python might deallocate th