Gregory Bond [EMAIL PROTECTED] writes:
I've had a solid hunt through the (2.3) documentation but it seems
silent on this issue.
I have an problem that would naturally run as 2 threads: One monitors
a bunch of asyncrhonous external state and decides if things are
good or bad. The second
I've had a solid hunt through the (2.3) documentation but it seems
silent on this issue.
I have an problem that would naturally run as 2 threads: One monitors a
bunch of asyncrhonous external state and decides if things are good or
bad. The second thread processes data, and the processing
Theoretically you have to use lock, while accesing the isgood instance,
but... practically noting bad can happen IN THIS PARTICULAR CASE, if
you don't. Python uses Global Interpreter Lock. In other words only
one thread is running at any particular moment. Thread scheduling is
preemptive, but
