Message354685
| Author | tim.peters |
|---|---|
| Recipients | Mark.Shannon, benjamin.peterson, christian.heimes, jdemeyer, larry, lukasz.langa, methane, miss-islington, nascheme, ned.deily, pablogsal, petr.viktorin, pitrou, tim.peters, vstinner |
| Date | 2019-10-15.03:01:38 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1571108498.55.0.505360007306.issue38006@roundup.psfhosted.org> |
| In-reply-to |
| Content | |
|---|---|
> While Neil & I haven't thought of ways that can go wrong now > beyond that a "surprise finalizer" may get run any number of > times ... Speaking of which, I no longer believe that's true. Thanks to the usual layers of baffling renaming via macro after macro, I missed object.c's PyObject_CallFinalizerFromDealloc(), which both respects and sets the "am I finalized?" flag regardless of how, e.g., an object with a __del__ ends its life (and possibly resurrects). |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2019-10-15 03:01:38 | tim.peters | set | recipients: + tim.peters, nascheme, pitrou, vstinner, larry, christian.heimes, benjamin.peterson, ned.deily, petr.viktorin, methane, lukasz.langa, Mark.Shannon, jdemeyer, pablogsal, miss-islington |
| 2019-10-15 03:01:38 | tim.peters | set | messageid: <1571108498.55.0.505360007306.issue38006@roundup.psfhosted.org> |
| 2019-10-15 03:01:38 | tim.peters | link | issue38006 messages |
| 2019-10-15 03:01:38 | tim.peters | create | |