On 01/31/2012 05:30 PM, mark florisson wrote:
On 31 January 2012 02:12, Robert Bradshaw<rober...@math.washington.edu> wrote:
On Fri, Jan 27, 2012 at 1:01 PM, Stefan Behnel<stefan...@behnel.de> wrote:
Dag Sverre Seljebotn, 27.01.2012 21:03:
the need to explicitly declare "except *" keeps coming up again and
again, and is really a blemish on the usability of Cython. When teaching
people Cython, then it's really irritating to have to follow "all you need
to do is add some 'cdef' and some types" with "and then you need to
remember to say "except *", or you're in deep trouble". Cython sort of
looks very elegant until that point...
I know what this feels like. The problem is that these things *are* complex.
Yes. We've been wrestling with this issue almost since Cython's inception...
I like Mark's two-function idea, with the caveat that f(bad_argument)
now behaves quite differently than (&f)[0](bad_argument) for even more
obscure reasons. But it may be the way to go.
Keep in mind that we talked about doing more or less the same to get rid
of "nogil"/"with gil". I believe that should be treated in the same
discussion. E.g., when doing
&f
you could get a version which acquires the GIL and which has a C ABI,
while calling f from Cython would step over the GIL-checking and has a
Cython-defined ABI.
Dag
_______________________________________________
cython-devel mailing list
cython-devel@python.org
http://mail.python.org/mailman/listinfo/cython-devel
