Re: [Cython] segfault in 'async def' coroutines

[Yury Selivanov]

On 2016-05-17 1:32 AM, Stefan Behnel wrote:

And finally, since both name values are guaranteed to be strings (the
setter checks their type), I wonder if we shouldn't just make sure they are
*exactly*  Unicode strings by converting any subtypes, and then remove their
Py_CLEAR() from the tp_clear() function. Strings can't participate in
reference cycles, and we could thus report the actual names even during
garbage collection.


This sounds like a really nice solution, Stefan.

Yury
___
cython-devel mailing list
cython-devel@python.org
https://mail.python.org/mailman/listinfo/cython-devel

Re: [Cython] Cygwin: Handling missing C99 long double functions

[Robert Bradshaw]

On Fri, May 13, 2016 at 4:26 AM, Erik Bray  wrote:
> On Thu, May 12, 2016 at 12:55 AM, Greg Ewing
>  wrote:
>> Erik Bray wrote:
>>>
>>> A developer who writes some code that
>>> happens to use long double isn't going to think themselves "Gosh, I
>>> guess I can't accept `long double` here because it may cause Cython to
>>> generate code that contains "truncl"
>>
>>
>> Sounds to me like Cython shouldn't be taking it upon
>> itself to generate calls to truncl just because long
>> double is being used. The programmer should have to
>> call it explicitly if that's what they want.
>
> Since it's just a small optimization it could be disabled without
> trouble too.  Preferably with a #define that can be set or unset at
> compile time.

https://github.com/cython/cython/commit/46d3efc4ff9123c73889bcb54b2b200d6be39ff4
___
cython-devel mailing list
cython-devel@python.org
https://mail.python.org/mailman/listinfo/cython-devel