[Python-Dev] Should execv() call _run_exitfuncs()? If not, should _run_exitfuncs() be private? (original) (raw)
rocky at gnu.org rocky at gnu.org
Sun Feb 1 11:17:29 CET 2009
- Previous message: [Python-Dev] Should execv() call _run_exitfuncs()? If not, should _run_exitfuncs() be private?
- Next message: [Python-Dev] Should execv() call _run_exitfuncs()? If not, should _run_exitfuncs() be private?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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).
- Previous message: [Python-Dev] Should execv() call _run_exitfuncs()? If not, should _run_exitfuncs() be private?
- Next message: [Python-Dev] Should execv() call _run_exitfuncs()? If not, should _run_exitfuncs() be private?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]