A RetroSearch Logo

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

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2009-February/085793.html below:

[Python-Dev] Should execv() call _run_exitfuncs()? If not, should _run_exitfuncs() be private?

[Python-Dev] Should execv() call _run_exitfuncs()? If not, should _run_exitfuncs() be private? [Python-Dev] Should execv() call _run_exitfuncs()? If not, should _run_exitfuncs() be private?rocky at gnu.org rocky at gnu.org
Sun Feb 1 11:17:29 CET 2009
Guido van Rossum writes:
 > Depending on the use for the exit function you might or might not want
 > it run at the occasion of exec*(). E.g. I imagine that in a typical
 > fork() + exec*() scenario, calling the exit functions in the child
 > process would be a mistake.
 > 
 > So I don't think the hooks should be called by default. However you
 > are welcome to call the function (leading underscore and all) if it
 > helps in your case.

Ok - got it. Thanks, everyone, for the clarification(s).
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