Re: Python/Tkinter crash.

2006-10-06 Thread Hendrik van Rooyen
"Steve Holden" <[EMAIL PROTECTED]> wrote: > Hendrik van Rooyen wrote: > > "Fredrik Lundh" <[EMAIL PROTECTED]> wrote: > > > >>Eric Brunel wrote: > >> > >> > >>>AFAIK, Tkinter is not thread safe. Using some kind of lock to serialize > >>>the calls from different threads may seem to work (I never test

Re: Python/Tkinter crash.

2006-10-05 Thread Steve Holden
Hendrik van Rooyen wrote: > "Fredrik Lundh" <[EMAIL PROTECTED]> wrote: > >>Eric Brunel wrote: >> >> >>>AFAIK, Tkinter is not thread safe. Using some kind of lock to serialize >>>the calls from different threads may seem to work (I never tested it >>>actually), but the safest way I found to use thr

Re: Python/Tkinter crash.

2006-10-05 Thread Hendrik van Rooyen
"Paul Rubin" wrote: > "Hendrik van Rooyen" <[EMAIL PROTECTED]> writes: > > I am not sure how to do this - once I have called the Tkinter > > mainloop - that main thread is essentially event driven - and > > figuring out how to get it to poll a queue for content is not >

Re: Python/Tkinter crash.

2006-10-05 Thread Hendrik van Rooyen
"Fredrik Lundh" <[EMAIL PROTECTED]> wrote: > Eric Brunel wrote: > > > AFAIK, Tkinter is not thread safe. Using some kind of lock to serialize > > the calls from different threads may seem to work (I never tested it > > actually), but the safest way I found to use threads with Tkinter was to > > cal

Re: Python/Tkinter crash.

2006-10-05 Thread Paul Rubin
"Hendrik van Rooyen" <[EMAIL PROTECTED]> writes: > I am not sure how to do this - once I have called the Tkinter > mainloop - that main thread is essentially event driven - and > figuring out how to get it to poll a queue for content is not > obvious - I suppose I could arrange some external wake u

Re: Python/Tkinter crash.

2006-10-05 Thread Hendrik van Rooyen
"Hendrik van Rooyen" <[EMAIL PROTECTED]> wrote: > "Eric Brunel" <[EMAIL PROTECTED]> wrote: > > > > On Wed, 04 Oct 2006 10:33:55 +0200, Hendrik van Rooyen > > <[EMAIL PROTECTED]> wrote: > > > > > Hi, > > > > > > I get the following: > > > > > > [EMAIL PROTECTED]:~/Controller/lib> python display.py

Re: Python/Tkinter crash.

2006-10-05 Thread Hendrik van Rooyen
"Russell E. Owen" <[EMAIL PROTECTED]> wrote: > In article <[EMAIL PROTECTED]>, > "Hendrik van Rooyen" <[EMAIL PROTECTED]> wrote: > > >Hi, > > > >I get the following: > > > >[EMAIL PROTECTED]:~/Controller/lib> python display.py > >UpdateStringProc should not be invoked for type font > >Aborted >

Re: Python/Tkinter crash.

2006-10-05 Thread Fredrik Lundh
Eric Brunel wrote: > AFAIK, Tkinter is not thread safe. Using some kind of lock to serialize > the calls from different threads may seem to work (I never tested it > actually), but the safest way I found to use threads with Tkinter was to > call it only from the thread where the main loop ex

Re: Python/Tkinter crash.

2006-10-05 Thread Eric Brunel
On Wed, 04 Oct 2006 20:02:56 +0200, Hendrik van Rooyen <[EMAIL PROTECTED]> wrote: > "Eric Brunel" <[EMAIL PROTECTED]> wrote: >> I know the problem happens sometimes on one of my Tkinter applications, >> but I never succeeded in reproducing it systematically. I've browsed the >> tcl bugs, but did

Re: Python/Tkinter crash.

2006-10-04 Thread Russell E. Owen
In article <[EMAIL PROTECTED]>, "Hendrik van Rooyen" <[EMAIL PROTECTED]> wrote: >Hi, > >I get the following: > >[EMAIL PROTECTED]:~/Controller/lib> python display.py >UpdateStringProc should not be invoked for type font >Aborted >... >Everything seems to work fine. - there is a thread that runs t

Re: Python/Tkinter crash.

2006-10-04 Thread Hendrik van Rooyen
"Eric Brunel" <[EMAIL PROTECTED]> wrote: > On Wed, 04 Oct 2006 10:33:55 +0200, Hendrik van Rooyen > <[EMAIL PROTECTED]> wrote: > > > Hi, > > > > I get the following: > > > > [EMAIL PROTECTED]:~/Controller/lib> python display.py > > UpdateStringProc should not be invoked for type font > > Aborte

Re: Python/Tkinter crash.

2006-10-04 Thread Eric Brunel
On Wed, 04 Oct 2006 10:33:55 +0200, Hendrik van Rooyen <[EMAIL PROTECTED]> wrote: > Hi, > > I get the following: > > [EMAIL PROTECTED]:~/Controller/lib> python display.py > UpdateStringProc should not be invoked for type font > Aborted > > and I am back at the bash prompt - this is most frustrat

Re: Python/Tkinter crash.

2006-10-04 Thread Hendrik van Rooyen
"James Stroud" <[EMAIL PROTECTED]> wrote: > Hendrik van Rooyen wrote: > > Hi, > > > > I get the following: > > > > [EMAIL PROTECTED]:~/Controller/lib> python display.py > > UpdateStringProc should not be invoked for type font > > Aborted > > > > and I am back at the bash prompt - this is most frus

Re: Python/Tkinter crash.

2006-10-04 Thread Hendrik van Rooyen
Not talking to myself - Added results of strace run at bottom "Hendrik van Rooyen" <[EMAIL PROTECTED]> wrote: > Hi, > > I get the following: > > [EMAIL PROTECTED]:~/Controller/lib> python display.py > UpdateStringProc should not be invoked for type font > Aborted > > and I am back at the bash

Re: Python/Tkinter crash.

2006-10-04 Thread James Stroud
Hendrik van Rooyen wrote: > Hi, > > I get the following: > > [EMAIL PROTECTED]:~/Controller/lib> python display.py > UpdateStringProc should not be invoked for type font > Aborted > > and I am back at the bash prompt - this is most frustrating, as there is no > friendly traceback to help me gues

Python/Tkinter crash.

2006-10-04 Thread Hendrik van Rooyen
Hi, I get the following: [EMAIL PROTECTED]:~/Controller/lib> python display.py UpdateStringProc should not be invoked for type font Aborted and I am back at the bash prompt - this is most frustrating, as there is no friendly traceback to help me guess where its coming from. And what is worse, t