This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author gvanrossum
Recipients georg.brandl, gvanrossum, jtonsing, loewis
Date 2007-09-14.19:40:48
SpamBayes Score 0.24917059
Marked as misclassified No
Message-id <1189798849.45.0.259421590514.issue1156@psf.upfronthosting.co.za>
In-reply-to
Content
> Should "child" be replaced with "parent"?

No.  I'm pretty much I wrote that.  The use case I was thinking of is
the error handling in the child process after the exec fails.  if you
were to use sys.exit() there, which raises SystemExit, you're likely to
hit various exception handlers that were set up in the parent, and you
even run the risk of some main loop continuing *in the child*.  I've had
many a program produce the phenomenon of "double tracebacks" due to this
mistake.

OTOH, in the parent, if you want to exit after forking (e.g. to create a
parent-less daemon process), a regular sys.exit() is usually just fine,
as any exception handlers you might trigger were meant to be triggered.
History
Date User Action Args
2007-09-14 19:40:49gvanrossumsetspambayes_score: 0.249171 -> 0.24917059
recipients: + gvanrossum, loewis, georg.brandl, jtonsing
2007-09-14 19:40:49gvanrossumsetspambayes_score: 0.249171 -> 0.249171
messageid: <1189798849.45.0.259421590514.issue1156@psf.upfronthosting.co.za>
2007-09-14 19:40:49gvanrossumlinkissue1156 messages
2007-09-14 19:40:48gvanrossumcreate