Re: [E-devel] Problem with legacy ecore stuff lifetime

2016-08-03 Thread The Rasterman
On Wed, 3 Aug 2016 19:47:47 +0200 Davide Andreoli said: > Ok, this has been fixed now in python bindings. > > The problem was that pyefl assume that every objects are Eo obj internally, > was coded this way at efl 1.8 and was a big Eo win that simplify a lot the > bindings (infact we rewrite qui

Re: [E-devel] Problem with legacy ecore stuff lifetime

2016-08-03 Thread Davide Andreoli
Ok, this has been fixed now in python bindings. The problem was that pyefl assume that every objects are Eo obj internally, was coded this way at efl 1.8 and was a big Eo win that simplify a lot the bindings (infact we rewrite quite everything at that time to use the Eo infra) We really use a lit

Re: [E-devel] Problem with legacy ecore stuff lifetime

2016-07-25 Thread Cedric BAIL
Hello, On Mon, Jul 25, 2016 at 12:59 PM, Davide Andreoli wrote: > lately quite all the ecore test we have in python-efl are failing for > (seems) the same reason: > > the del callback seems not be called when you return FALSE from a callback > that should delete the object in that case, Animator

[E-devel] Problem with legacy ecore stuff lifetime

2016-07-25 Thread Davide Andreoli
Hi all, lately quite all the ecore test we have in python-efl are failing for (seems) the same reason: the del callback seems not be called when you return FALSE from a callback that should delete the object in that case, Animator fe. I'm quite sure this is not a python related issue but I have n