Re: [sage-devel] Re: [sage-trac] #26795: Some memory leaks

2018-12-03 Thread Dima Pasechnik
Thanks everyone, __dealloc__ works marvellously. That poor __desrtuct__() was never called (except by a sort of meaningless doctesting), since it got there in 2011... Actually, I wonder if there is a regular way to doctest destructors like this one. On Mon, Dec 3, 2018 at 4:19 PM Vincent Delecroi

Re: [sage-devel] Re: [sage-trac] #26795: Some memory leaks

2018-12-03 Thread Vincent Delecroix
Old or new, C-allocator is __cinit__ and C-deallocator is __dealloc__. The __destruct__ method is not special in any way (beyond the fact that it starts and ends by two underscores). Le 03/12/2018 à 17:07, Dima Pasechnik a écrit : It is old code. And there is no __cinit__, only __init__ On Mon

Re: [sage-devel] Re: [sage-trac] #26795: Some memory leaks

2018-12-03 Thread Dima Pasechnik
It is old code. And there is no __cinit__, only __init__ On Mon, 3 Dec 2018 15:56 Nils Bruin Is there something new in cython that makes __destruct__ a special method? > I thought __dealloc__ was the place to undo __cinit__ stuff. > > On Monday, December 3, 2018 at 7:29:14 AM UTC-8, Dima Pasechn

[sage-devel] Re: [sage-trac] #26795: Some memory leaks

2018-12-03 Thread Nils Bruin
Is there something new in cython that makes __destruct__ a special method? I thought __dealloc__ was the place to undo __cinit__ stuff. On Monday, December 3, 2018 at 7:29:14 AM UTC-8, Dima Pasechnik wrote: > > An expert in Cython/Python classes needed: __destruct__ is not called for > a reason