Gregory P. Smith greg at krypto.org
Fri Sep 8 15:57:10 EDT 2017

• Previous message (by thread): [Python-Dev] PEP 556: Threaded garbage collection
• Next message (by thread): [Python-Dev] PEP 556: Threaded garbage collection
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

On Fri, Sep 8, 2017 at 12:52 PM Antoine Pitrou <solipsis at pitrou.net> wrote:

> On Fri, 8 Sep 2017 12:40:34 -0700
> Nathaniel Smith <njs at pobox.com> wrote:
> >
> > PyPy just abandons everything when shutting down, instead of running
> > finalizers. See the last paragraph of :
> >
> http://doc.pypy.org/en/latest/cpython_differences.html#differences-related-to-garbage-collection-strategies
> >
> > So that might be a useful source of experience.
>
> CPython can be embedded in applications, though, and that is why we try
> to be a bit more thorough during the interpreter cleanup phase.
>

Indeed.  My gut feeling is that proposing to not run finalizers on
interpreter shutdown is a non-starter and would get the pep rejected.
We've previously guaranteed that they were run unless the process dies via
an unhandled signal or calls os._exit() in CPython.

-gps
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20170908/60ffe976/attachment.html>

---

• Previous message (by thread): [Python-Dev] PEP 556: Threaded garbage collection
• Next message (by thread): [Python-Dev] PEP 556: Threaded garbage collection
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-Dev mailing list