Message161779
| Author |
pitrou |
| Recipients |
neologix, pitrou, sbt, skrah |
| Date |
2012年05月28日.13:13:23 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1338210629.3328.4.camel@localhost.localdomain> |
| In-reply-to |
<1338209403.75.0.837880370451.issue14930@psf.upfronthosting.co.za> |
| Content |
> Doing it after Py_CLEAR(self->mbuf) seems to contradict
>
> http://docs.python.org/dev/extending/newtypes.html?highlight=pyobject_clearweakrefs#weak-reference-support
>
> which says
>
> The only further addition is that the destructor needs to call the weak
> reference manager to clear any weak references. This should be done *before*
> any other parts of the destruction have occurred, but is only required if the
> weak reference list is non-NULL:
Mmh, this seems to be misled. The original formulation is from SVN
r16381; the clearly erroneous part about resurrecting objects was later
removed in r18223, but the rest is probably unnecessary as well. I'll
open a separate issue. |
|