homepage

This issue tracker has been migrated to GitHub , and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pitrou
Recipients kristjan.jonsson, pitrou, tim.peters
Date 2010年07月04日.17:17:14
SpamBayes Score 0.008617872
Marked as misclassified No
Message-id <1278263831.3250.14.camel@localhost.localdomain>
In-reply-to <1278263465.31.0.812372812479.issue9141@psf.upfronthosting.co.za>
Content
> A finalizer _may_ be tp_del, but it may be any code that is called as
> part of tp_dealloc(). This patch allows an object to say: Calling
> tp_dealloc() is currently unsafe from a gc.collect() run.
Well, I don't know what you mean. tp_dealloc should always be "safe" and
is never checked for by the GC.
By the way, tp_del isn't even documented, which reinforces my point that
it's not really for use by third-party extension types.
I think we are reaching the point where, if you want this to happen, you
should ask for opinions on python-dev, because I really don't understand
which problem you are trying to solve.
History
Date User Action Args
2010年07月04日 17:17:16pitrousetrecipients: + pitrou, tim.peters, kristjan.jonsson
2010年07月04日 17:17:14pitroulinkissue9141 messages
2010年07月04日 17:17:14pitroucreate

AltStyle によって変換されたページ (->オリジナル) /