Re: [sage-devel] Python 2.7.13rc1 breaks UnknownClass

2016-12-10 Thread Tobias Hansen
On 12/09/2016 09:54 PM, Nicolas M. Thiery wrote: > On Wed, Dec 07, 2016 at 02:50:15PM +, Tobias Hansen wrote: >> On 12/07/2016 01:26 PM, Jeroen Demeyer wrote: >> If you look at the patch [1] that was applied, there is a new check for >> tp_new(). I'm not 100% sure that's what causes the

Re: [sage-devel] Python 2.7.13rc1 breaks UnknownClass

2016-12-09 Thread Nicolas M. Thiery
On Wed, Dec 07, 2016 at 02:50:15PM +, Tobias Hansen wrote: > On 12/07/2016 01:26 PM, Jeroen Demeyer wrote: > If you look at the patch [1] that was applied, there is a new check for > tp_new(). I'm not 100% sure that's what causes the problem, but it looks > suspicious. > > [1]

Re: [sage-devel] Python 2.7.13rc1 breaks UnknownClass

2016-12-07 Thread Tobias Hansen
On 12/07/2016 01:26 PM, Jeroen Demeyer wrote: > What is the problem really? Neither from reading the bug report nor from > reading this thread do I understand what exactly changed in Python > 2.7.13 causing this breakage. > If you look at the patch [1] that was applied, there is a new check for

Re: [sage-devel] Python 2.7.13rc1 breaks UnknownClass

2016-12-07 Thread Jeroen Demeyer
I created a ticket for this upgrade: https://trac.sagemath.org/ticket/22037 But we should first upgrade to Python 2.7.12 before we can tackle 2.7.13: https://trac.sagemath.org/ticket/19735 Anyone willing to work on the Python 2.7.12 upgrade? It would at least make it easier to debug the

Re: [sage-devel] Python 2.7.13rc1 breaks UnknownClass

2016-12-07 Thread Jeroen Demeyer
What is the problem really? Neither from reading the bug report nor from reading this thread do I understand what exactly changed in Python 2.7.13 causing this breakage. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this

Re: [sage-devel] Python 2.7.13rc1 breaks UnknownClass

2016-12-07 Thread Tobias Hansen
On 12/07/2016 11:07 AM, Tobias Hansen wrote: > On 12/07/2016 10:57 AM, Francois Bissey wrote: >> >>> On 7/12/2016, at 21:15, Jeroen Demeyer wrote: >>> >>> On 2016-12-07 04:17, Francois Bissey wrote: But I am not sure how to do the __new__ = object.__new__ in

Re: [sage-devel] Python 2.7.13rc1 breaks UnknownClass

2016-12-07 Thread Tobias Hansen
On 12/07/2016 10:57 AM, Francois Bissey wrote: > >> On 7/12/2016, at 21:15, Jeroen Demeyer wrote: >> >> On 2016-12-07 04:17, Francois Bissey wrote: >>> But I am not sure how to do the >>> __new__ = object.__new__ in cython. >> >> You certainly cannot do that since

Re: [sage-devel] Python 2.7.13rc1 breaks UnknownClass

2016-12-07 Thread Francois Bissey
> On 7/12/2016, at 21:15, Jeroen Demeyer wrote: > > On 2016-12-07 04:17, Francois Bissey wrote: >> But I am not sure how to do the >> __new__ = object.__new__ in cython. > > You certainly cannot do that since Cython's __new__ does non-trivial stuff > like setting the

Re: [sage-devel] Python 2.7.13rc1 breaks UnknownClass

2016-12-07 Thread Jeroen Demeyer
On 2016-12-07 04:17, Francois Bissey wrote: But I am not sure how to do the __new__ = object.__new__ in cython. You certainly cannot do that since Cython's __new__ does non-trivial stuff like setting the vtab for c(p)def method calls. This is also partially the reason why cannot even

Re: [sage-devel] Python 2.7.13rc1 breaks UnknownClass

2016-12-06 Thread Francois Bissey
I am guessing we should something more fundamental in sage/structure/sage_object.pyx since we are dealing with SageObject classes. But I am not sure how to do the __new__ = object.__new__ in cython. François > On 7/12/2016, at 15:25, than...@debian.org wrote: > > When setting __new__ =

Re: [sage-devel] Python 2.7.13rc1 breaks UnknownClass

2016-12-06 Thread than...@debian.org
Am Mittwoch, 7. Dezember 2016 01:43:09 UTC schrieb tha...@debian.org: > > On 12/07/2016 01:27 AM, François Bissey wrote: > > On 07/12/16 12:20, tha...@debian.org wrote: > >> Hi sage-devel, > >> > >> we're almost ready to upload Sage to Debian (in fact we basically have >

Re: [sage-devel] Python 2.7.13rc1 breaks UnknownClass

2016-12-06 Thread Tobias Hansen
On 12/07/2016 01:27 AM, François Bissey wrote: > On 07/12/16 12:20, than...@debian.org wrote: >> Hi sage-devel, >> >> we're almost ready to upload Sage to Debian (in fact we basically have >> to upload it this week to make sure it's included in the next Debian >> release). >> >> However, on Sunday

Re: [sage-devel] Python 2.7.13rc1 breaks UnknownClass

2016-12-06 Thread François Bissey
On 07/12/16 12:20, than...@debian.org wrote: Hi sage-devel, we're almost ready to upload Sage to Debian (in fact we basically have to upload it this week to make sure it's included in the next Debian release). However, on Sunday python 2.7.13rc1 was uploaded to Debian and now we are facing a

[sage-devel] Python 2.7.13rc1 breaks UnknownClass

2016-12-06 Thread than...@debian.org
Hi sage-devel, we're almost ready to upload Sage to Debian (in fact we basically have to upload it this week to make sure it's included in the next Debian release). However, on Sunday python 2.7.13rc1 was uploaded to Debian and now we are facing a bug that I didn't quite manage to work around