Re: [Cython] GIL handling C code

2012-02-28 Thread mark florisson
On 28 February 2012 21:38, Stefan Behnel wrote: > mark florisson, 28.02.2012 22:19: >> On 28 February 2012 21:08, Stefan Behnel wrote: >>> mark florisson, 28.02.2012 21:20: On 28 February 2012 19:58, Stefan Behnel wrote: > mark florisson, 28.02.2012 16:35: >> Basically, the cleanup co

Re: [Cython] GIL handling C code

2012-02-28 Thread Stefan Behnel
mark florisson, 28.02.2012 22:19: > On 28 February 2012 21:08, Stefan Behnel wrote: >> mark florisson, 28.02.2012 21:20: >>> On 28 February 2012 19:58, Stefan Behnel wrote: mark florisson, 28.02.2012 16:35: > Basically, the cleanup code only needs a matching release because the > corre

Re: [Cython] GIL handling C code

2012-02-28 Thread mark florisson
On 28 February 2012 21:22, Stefan Behnel wrote: > mark florisson, 28.02.2012 22:09: >> On 28 February 2012 21:08, mark florisson wrote: >>> On 28 February 2012 20:19, Stefan Behnel wrote: Stefan Behnel, 28.02.2012 20:58: > mark florisson, 28.02.2012 16:35: >> Basically, the cleanup co

Re: [Cython] GIL handling C code

2012-02-28 Thread Stefan Behnel
mark florisson, 28.02.2012 22:09: > On 28 February 2012 21:08, mark florisson wrote: >> On 28 February 2012 20:19, Stefan Behnel wrote: >>> Stefan Behnel, 28.02.2012 20:58: mark florisson, 28.02.2012 16:35: > Basically, the cleanup code only needs a matching release because the > corre

Re: [Cython] GIL handling C code

2012-02-28 Thread mark florisson
On 28 February 2012 21:08, Stefan Behnel wrote: > mark florisson, 28.02.2012 21:20: >> On 28 February 2012 19:58, Stefan Behnel wrote: >>> mark florisson, 28.02.2012 16:35: Basically, the cleanup code only needs a matching release because the corresponding acquire is in EnsureGILNode, wh

Re: [Cython] GIL handling C code

2012-02-28 Thread mark florisson
On 28 February 2012 21:08, Stefan Behnel wrote: > mark florisson, 28.02.2012 21:20: >> On 28 February 2012 19:58, Stefan Behnel wrote: >>> mark florisson, 28.02.2012 16:35: Basically, the cleanup code only needs a matching release because the corresponding acquire is in EnsureGILNode, wh

Re: [Cython] GIL handling C code

2012-02-28 Thread mark florisson
On 28 February 2012 21:08, mark florisson wrote: > On 28 February 2012 20:19, Stefan Behnel wrote: >> Stefan Behnel, 28.02.2012 20:58: >>> mark florisson, 28.02.2012 16:35: Basically, the cleanup code only needs a matching release because the corresponding acquire is in EnsureGILNode, w

Re: [Cython] GIL handling C code

2012-02-28 Thread Stefan Behnel
mark florisson, 28.02.2012 21:20: > On 28 February 2012 19:58, Stefan Behnel wrote: >> mark florisson, 28.02.2012 16:35: >>> Basically, the cleanup code only needs a matching release because the >>> corresponding acquire is in EnsureGILNode, which wraps the function >>> body in case of a nogil func

Re: [Cython] GIL handling C code

2012-02-28 Thread mark florisson
On 28 February 2012 20:19, Stefan Behnel wrote: > Stefan Behnel, 28.02.2012 20:58: >> mark florisson, 28.02.2012 16:35: >>> Basically, the cleanup code only needs a matching release because the >>> corresponding acquire is in EnsureGILNode, which wraps the function >>> body in case of a nogil func

Re: [Cython] GIL handling C code (was: [cython-users] What's up with PyEval_InitThreads() in python 2.7?)

2012-02-28 Thread mark florisson
On 28 February 2012 19:58, Stefan Behnel wrote: > mark florisson, 28.02.2012 16:35: >> Basically, the cleanup code only needs a matching release because the >> corresponding acquire is in EnsureGILNode, which wraps the function >> body in case of a nogil function with a 'with gil' block. Any chang

Re: [Cython] GIL handling C code

2012-02-28 Thread Stefan Behnel
Stefan Behnel, 28.02.2012 20:58: > mark florisson, 28.02.2012 16:35: >> Basically, the cleanup code only needs a matching release because the >> corresponding acquire is in EnsureGILNode, which wraps the function >> body in case of a nogil function with a 'with gil' block. Any changes >> to the con

Re: [Cython] GIL handling C code (was: [cython-users] What's up with PyEval_InitThreads() in python 2.7?)

2012-02-28 Thread Stefan Behnel
mark florisson, 28.02.2012 16:35: > Basically, the cleanup code only needs a matching release because the > corresponding acquire is in EnsureGILNode, which wraps the function > body in case of a nogil function with a 'with gil' block. Any changes > to the conditions in FuncDefNode will have to be