Thomas Wouters wrote:
It seems that, on my platform at least, Tk_Init() doesn't like being
called twice even when the first call resulted in an error. That's Tcl
and Tk 8.4.12. Tkapp_Init() (which is the Tkinter part that calls
Tk_Init()) does its best to guard against calling Tk_Init() twice
Thanks Martin!
Jeff
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Jeff Epler wrote:
However, on this system, I couldn't recreate the problem you reported
with either the using _tkinter directly instructions, or using this
C test program:
#include tcl.h
#include tk.h
int main(void) {
Tcl_Interp *trp;
unsetenv(DISPLAY);
trp =
On 4/24/06, Jeff Epler [EMAIL PROTECTED] wrote:
I just read the manpage for Tk_Init(3) (fc4 package tk-8.4.9-3) and itdoes not say that Tk_Init() may only be called once.While this doesn'tmean Python shouldn't work around it, I think the behavior should be
considered a bug in Tk, not
For a while now, I've noticed test_tcl locking up when trying to refleaktest it. I was able to reproduce it quite simply:import Tkinterimport osif DISPLAY in os.environ: del os.environ
[DISPLAY]tcl = Tkinter.Tcl()try: tcl.loadtk()except Exception, e: print etcl.loadtk()Or, more directly, using
I just read the manpage for Tk_Init(3) (fc4 package tk-8.4.9-3) and it
does not say that Tk_Init() may only be called once. While this doesn't
mean Python shouldn't work around it, I think the behavior should be
considered a bug in Tk, not _tkinter.
However, on this system, I couldn't recreate
