Home Original page

"RuntimeError: Calling Tcl from different appartment"

Aahz aahz at pythoncraft.com
Mon Jun 21 11:16:06 EDT 2004 
In article <ced73313.0406210646.72fddfe4 at posting.google.com>,
Peter Saffrey <theoryboy at my-deja.com> wrote:
>
>I am writing a multi-threaded Tkinter application. It worked fine with
>Python 2.2 under Redhat 8.0, but I have recently moved across to
>Debian (testing/unstable) and Python 2.3. Now I get the above error
>message.
>
>I read on this group somewhere that this is caused by calling Tk
>functions from a different thread to where the interface is running.

Yup.

>Unfortunately, I really need to do this and cannot have all my Tk
>calls within one thread. Is there a way around this? Why did it work
>in 2.2 but not 2.3?

No clue why it used to work.  Why do you need to call Tk from multiple
threads?
-- 
Aahz (aahz at pythoncraft.com)           <*>         http://www.pythoncraft.com/

"Typing is cheap.  Thinking is expensive."  --Roy Smith, c.l.py
More information about the Python-list mailing list