On Nov 9, 2009, at 9:44 AM, Stefan Behnel wrote:
> Chris Colbert, 09.11.2009 18:40:
>> What was the rationality behind having to explicitly declare C
>> division, versus explicitly declaring python division?
This is a very good question, and if you look at the links below (and
the discussions o
Chris Colbert, 09.11.2009 18:40:
> What was the rationality behind having to explicitly declare C
> division, versus explicitly declaring python division?
Python code semantics.
http://wiki.cython.org/enhancements/division
http://thread.gmane.org/gmane.comp.python.cython.devel/4769/focus=4938
S
What was the rationality behind having to explicitly declare C
division, versus explicitly declaring python division?
Just curious.
Cheers!
On Mon, Nov 9, 2009 at 5:40 PM, Dag Sverre Seljebotn
wrote:
>> Hi all,
>>
>> Why is it necessary to decorate a pure "cdef" with
>> @cython.cdivision(True
> Hi all,
>
> Why is it necessary to decorate a pure "cdef" with
> @cython.cdivision(True) in order to release the gil?
>
> If I missed the discussion on this somewhere, feel free to just refer
> me back to the archive.
If there's a division by zero in Python division mode, an exception must
be ra
Stéfan van der Walt wrote:
> Why is it necessary to decorate a pure "cdef" with
> @cython.cdivision(True) in order to release the gil?
Probably because otherwise it assumes Python semantics
for division, which requires making Python API calls,
so the GIL is needed.
--
Greg
Hi all,
Why is it necessary to decorate a pure "cdef" with
@cython.cdivision(True) in order to release the gil?
If I missed the discussion on this somewhere, feel free to just refer
me back to the archive.
Thanks!
Stéfan
___
Cython-dev mailing list
Cyt
