On Nov 15, 2007 4:50 AM, <[EMAIL PROTECTED]> wrote:
> Many thanks for the clarification. Also good idea to focus on lock
> ownership rather that thread activity in your diagram.
>
> To be honest I was not actually experiencing deadlock issues. I had
> just deduced (incorrectly) that I might do so
Many thanks for the clarification. Also good idea to focus on lock
ownership rather that thread activity in your diagram.
To be honest I was not actually experiencing deadlock issues. I had
just deduced (incorrectly) that I might do so if I started using locks
in my py code called from c-land. As
On Nov 12, 2007 6:56 AM, <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I have a native windows thread in a c python module which calls into
> python code and adds an item to a data structure (a home-grown
> circular buffer). At the same time my main python application is
> removing items from this data str
Hi,
I have a native windows thread in a c python module which calls into
python code and adds an item to a data structure (a home-grown
circular buffer). At the same time my main python application is
removing items from this data structure.
Unlike native python containers adding and removing ite
