[Debian-science-sagemath] Sage broken with Python 2.7.13~rc1-1

[Tobias Hansen]

Actually forget my last mail. It seems to be Issue #5322. In the commit
there is this new comment in Objects/typeobject.c:

                    /* Seems to be unsafe, better use
                       slot_tp_new which will call
                       tp_new_wrapper which will raise an
                       exception if it is unsafe. */

Something like that seems to happen.

On 12/06/2016 05:53 PM, Ximin Luo wrote:
> Ouch, nice catch. I actually did notice that a new version of python had been uploaded by running `debian/show-deps.sh by-date` but ignored it because "oh it can't possibly be a python bug". I guess it's worth paying attention to the output of that for the future.
> 
> X
> 
> Tobias Hansen:
>> Actually it looks more related to https://bugs.python.org/issue24469
>>
>> From the changelog:
>> Issue #24469: Fixed memory leak caused by int subclasses without
>> overridden tp_free (e.g. C-inherited Cython classes).
>>
>> And our error happens at tp_free in sage/misc/classcall_metaclass.pyx
>>
>> On 12/06/2016 05:32 PM, Tobias Hansen wrote:
>>> Hi all,
>>>
>>> there was an update to python2.7 on Sunday that unfortunately broke
>>> building or even running sage. The error one gets is this:
>>>
>>> TypeError: sage.misc.fast_methods.WithEqualityById.__new__(UnknownClass)
>>> is not safe, use object.__new__()
>>>
>>> In the changelog it of python2.7 there is this entry:
>>> Issue #5322: Fixed setting __new__ to a PyCFunction inside Python code.
>>>
>>> leading to this bug report:
>>> https://bugs.python.org/issue5322
>>>
>>> I just found this, just wanted to let you know why nothing works.
>>>
>