[issue32377] Difference in ressurrection behavior with __del__ in py2 vs. py3

Eric Cousineau added the comment: See also bpo-40240: "Expose public spelling of _PyGC_FINALIZED and _PyGC_SET_FINALIZED?" -- ___ Python tracker ___

[issue32377] Difference in ressurrection behavior with __del__ in py2 vs. py3

Eric Cousineau added the comment: Super late response, but for this part: > Well... perhaps you could create another PyObject (it's just a wrapper, > right?) since the old one doesn't have any outside references to it > remaining. In certain cases, yes, that would be the case. I do have

[issue32377] Difference in ressurrection behavior with __del__ in py2 vs. py3

Change by Antoine Pitrou : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue32377] Difference in ressurrection behavior with __del__ in py2 vs. py3

Antoine Pitrou added the comment: New changeset dc5770b161a5e28eeff73a406cd4eddb0676c5b5 by Antoine Pitrou (Miss Islington (bot)) in branch '3.6': bpo-32377: improve __del__ docs and fix mention about resurrection (GH-4927) (#4929)

[issue32377] Difference in ressurrection behavior with __del__ in py2 vs. py3

Antoine Pitrou added the comment: New changeset 4b965930e8625f77cb0e821daf5cc40e85b45f84 by Antoine Pitrou in branch 'master': bpo-32377: improve __del__ docs and fix mention about resurrection (#4927)

[issue32377] Difference in ressurrection behavior with __del__ in py2 vs. py3

Change by Roundup Robot : -- pull_requests: +4823 ___ Python tracker ___

[issue32377] Difference in ressurrection behavior with __del__ in py2 vs. py3

Antoine Pitrou added the comment: I've proposed a documentation improvement in https://github.com/python/cpython/pull/4927 . Please chime in if you see have issues with it. -- ___ Python tracker

[issue32377] Difference in ressurrection behavior with __del__ in py2 vs. py3

Change by Antoine Pitrou : -- keywords: +patch pull_requests: +4822 stage: needs patch -> patch review ___ Python tracker ___

[issue32377] Difference in ressurrection behavior with __del__ in py2 vs. py3

Antoine Pitrou added the comment: Le 19/12/2017 à 17:46, Eric Cousineau a écrit : > > My current hack is to call `_PyGC_SET_FINALIZED(self, 0)` - may I ask if > there is a simpler way to do this? Well... perhaps you could create another PyObject (it's just a wrapper, right?)

[issue32377] Difference in ressurrection behavior with __del__ in py2 vs. py3

Eric Cousineau added the comment: You're welcome, and thank you for the prompt response! I will say that it feels a tad odd to only have `tp_finalize` be called once for the entire lifetime of the object, while still having the option of it being resurrected. Is

[issue32377] Difference in ressurrection behavior with __del__ in py2 vs. py3

Antoine Pitrou added the comment: Thanks for the report. Apparently I forgot to update that piece of documentation when PEP 442 was implemented. -- nosy: +pitrou stage: -> needs patch versions: +Python 3.7 -Python 3.4, Python 3.5

[issue32377] Difference in ressurrection behavior with __del__ in py2 vs. py3

New submission from Eric Cousineau : Due to how `PyObject_CallFinalizer` is written in python3, `__del__` will only *ever* be called once. In my use case, I am experimenting with a feature in `pybind11` to prevent slicing with Python class instances that inherit