> please don't top-post. Well excuse me. :) I didn't notice Gmail was stuffing the whole thing under my reply.
> I think this is the one case where exception propagation will easily work > in a nogil block. If we get the exception propagation semantics right here, > we can leave this in. But it's not entirely clear (at least to me) if this > currently behaves 'correctly'. OK, it sounds like I should rework this so that it fits better with the current defined behavior of Cython, to avoid unexpected breakage. > It *might* be possible to enable the same for "except *" somehow, but until > then, Cython should raise an error at compile time rather than letting the > code crash at runtime. I agree, this shouldn't even compile with "except *"; re-acquiring the GIL inside a nogil block every time an "except-*" declared function returns seems like it's too surprising, especially in the (common) case of infrequently raised exceptions. Nogil code shouldn't touch the GIL unless it really, really has to. Thanks, Andrew Collette _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
