rats, and I was determined to figure it out myself. Between corba,
orbit, and extending the python interpreter, plus the threads code, it
was taking me longer to wade throught it all than I thought.
I had noticed that the tcl/tk module had essentially the same conditions
for locking. So I was using it as a model.
One piece of wisdom that I picked up from that work (_tkinter) was the
fact that they have another lock that only lets one thread run inside
the tcl interpreter at a time. I was concerned about this for the
orbit-python module.
Essentially they only hold the global interpreter lock or the tk lock
exclusive (except for special cases) of each other. I imagine this
may still be a problem? Or do you think this is a non issue?
jb
Jason Tackaberry writes:
> I added the appropriate locks/unlocks to the code to support threading in
> Python. I tested it briefly and it seems to work, but there still may be
> problems. It only took me a couple minutes, and I'm skeptical to think
> anything is that simple. :) Let me know if you run into any bugs.
>
> >From the ChangeLog:
>
> * server.c, client.c, CORBA_ORB.c: added necessary interpreter unlocking
> to support Python threads properly. (Not very tested, but seems to
> work.)
>
> Jason.
--
------------------+
Joseph T. Bore |
jb...@TJ... |
------------------+
|
