On Jul 23, 11:29 pm, Nick Craig-Wood n...@craig-wood.com wrote:
The syntax would be something like:
def work():
showstatus(building)
r = yield runshell(make)
showstatus(installing)
r = yield runshell(make install)
showstatus(Success)
mygui.startwork(work)
#
Apologies for the long subject line, here it is again:
Pep 342 (val = yield MyGenerator(foo)), synchronous os.system() that
doesn't block gui event loops
On Jul 21, 7:48 pm, John Nagle na...@animats.com wrote:
The idea:
To run functions that execute a series of system commands without
Ville Vainio vivai...@gmail.com wrote:
Has anyone implementing something like what the subject line
indicates?
The idea:
To run functions that execute a series of system commands without
blocking the ui, *and* without adding state machine logic.
The syntax would be something
Ville Vainio wrote:
Has anyone implementing something like what the subject line
indicates?
The idea:
To run functions that execute a series of system commands without
blocking the ui, *and* without adding state machine logic.
At some level, there's going to be state machine logic.
You
Ville Vainio wrote:
Has anyone implementing something like what the subject line
indicates?
Your subject line is so long that it is cut off even on my wide screen.
Better to repeat the question in the body.
--
http://mail.python.org/mailman/listinfo/python-list
Has anyone implementing something like what the subject line
indicates?
The idea:
To run functions that execute a series of system commands without
blocking the ui, *and* without adding state machine logic.
The syntax would be something like:
def work():
showstatus(building)
r = yield
On Jul 20, 1:12 pm, Ville Vainio vivai...@gmail.com wrote:
Has anyone implementing something like what the subject line
ImplentED.
I don't think this is that hard to do in the first place, but a
generic solution that can be easily tuned for different gui
mainloops would be nice.
--
On Jul 20, 1:12 pm, Ville Vainio vivai...@gmail.com wrote:
I imagine runshell() would be implemented in terms of QProcess, or
subprocess.Popen/os.system and a worker thread.
Actually, the problem is that of general serialization of worker
thread operations. That is, it could be something akin
