A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from http://mail.python.org/pipermail/python-dev/2017-September/149385.html below:

[Python-Dev] PEP 556: Threaded garbage collection

[Python-Dev] PEP 556: Threaded garbage collection [Python-Dev] PEP 556: Threaded garbage collectionBenjamin Peterson benjamin at python.org
Fri Sep 8 15:04:10 EDT 2017
I like it overall.

- I was wondering what happens during interpreter shutdown. I see you
have that listed as a open issue. How about simply shutting down the
finalization thread and not guaranteeing that finalizers are actually
ever run à la Java?

- Why not run all (Python) finalizers on the thread and not just ones
from cycles?

On Fri, Sep 8, 2017, at 08:05, Antoine Pitrou wrote:
> 
> Hello,
> 
> I've written a PEP by which you can tell the GC to run in a dedicated
> thread.  The goal is to solve reentrancy issues with finalizers:
> https://www.python.org/dev/peps/pep-0556/
> 
> Regards
> 
> Antoine.
> 
> PS: I did not come up with the idea for this PEP while other people
> were having nightmares.  Any nightmares involved in this PEP are
> fictional, and any resemblance to actual nightmares is purely
> coincidental.  No nightmares were harmed while writing this PEP.
> 
> _______________________________________________
> Python-Dev mailing list
> Python-Dev at python.org
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
> https://mail.python.org/mailman/options/python-dev/benjamin%40python.org
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4