[Python-Dev] tp_finalize vs tp_del sematics (original) (raw)
Valentine Sinitsyn valentine.sinitsyn at gmail.com
Thu Sep 3 09:23:48 CEST 2015
- Previous message (by thread): [Python-Dev] Request a builedbot username and password
- Next message (by thread): [Python-Dev] tp_finalize vs tp_del sematics
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi Armin,
On 25.08.2015 13:00, Armin Rigo wrote:
Hi Valentine,
On 25 August 2015 at 09:56, Valentine Sinitsyn <valentine.sinitsyn at gmail.com> wrote:
Yes, I think so. There is a highly obscure corner case: del will still be called several times if you declare your class with "slots=()".
Even on "post-PEP-0442" Python 3.4+? Could you share a link please? class X(object): slots=() # <= try with and without this def del(self): global revive revive = self print("hi") X() revive = None revive = None revive = None By accident, I found a solution to this puzzle:
class X(object): slots = ()
class Y(object): pass
import gc gc.is_tracked(X()) # False gc.is_tracked(Y()) # True
An object with empty slots is naturally untracked, as it can't create back references.
Valentine
- Previous message (by thread): [Python-Dev] Request a builedbot username and password
- Next message (by thread): [Python-Dev] tp_finalize vs tp_del sematics
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]