On Sat, Aug 20, 2011 at 2:55 AM, mark florisson
wrote:
> On 20 August 2011 00:34, mark florisson wrote:
>> Hey,
>>
>> I think I found a rather serious bug: if an error label is used in a
>> nogil function, it tries to build a traceback. So if the GIL is
>> released you will immediately segfault,
On 20 August 2011 06:55, mark florisson wrote:
>
> What about the syntax issue though? Should we fix that?
>
Long ago I also complained about that. Greg commented that we should
really accept "except" and "gil/nogil" in any position, so that
cdef int foo() except 0 with gil
cdef int foo() with g
On 20 August 2011 00:34, mark florisson wrote:
> Hey,
>
> I think I found a rather serious bug: if an error label is used in a
> nogil function, it tries to build a traceback. So if the GIL is
> released you will immediately segfault, and otherwise it will work
> fine! Here is a snippet:
>
> cdef
Hey,
I think I found a rather serious bug: if an error label is used in a
nogil function, it tries to build a traceback. So if the GIL is
released you will immediately segfault, and otherwise it will work
fine! Here is a snippet:
cdef int with_gil_func() except 0 with gil:
raise Exception("er
