Jim Weirich wrote:

> 
> In Ruby, the finalizer is not run until *after* the object is collected. 
> Since the object itself is no longer around, there is no possibility of 
> even accidently creating a new reference to the object.  It also means 
> that the finalizer can't be an instance method (because the instance is 
> gone when the finalizer is run).


This makes perfect sense since Ruby uses mark&sweep. But in Python is it 
possible to supply __del__ method which seems to be an instance one 
(correct me if I'm wrong), but the moment of GC cannot be determined 
anyways. And as rmagick mentioned, explicit destrutors are not needed 
anyways.

lopex