> if there is a down fall with python 2.x I think it's 'threading'. If I were you I'd move to python 3.x
>and use all the threading tools coming out. I tried to do some with a long running process without
>much success using 2.7. I ended up creating a cron job to setup some temporary tables that
>were later used for the processing.

Your input is welcome.

My intention is to wait until wx is available on 3.x to start serious work - I have a lot to code
that is not UI related - and work with both threading for a responsive UI and one long running
process for data crunching. I understand that this may require a timer run in the alternate
thread on top of the main used for the UI. This timer getting dequeuing the work done in
the long running processes.

Does not looks simple. If I discover that this can be avoided (via cython optimization), I'll try to!

For the moment, this is all vaporware anyway. The vfp code still runs well. And this rewrite is
obviousy neeeded - as a long term perspective - but certainly not desperately so:)

>BTW do not buy the pyQT book - it's way out dated.

Too late:) Bought and read (was a couple of years ago...). I did not find comfortable with the
UI mechanics. A tad too far for from our vb, vfp biases I expect.

François