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 neologix
Recipients davin, eryksun, neologix, pietvo, pitrou, sbt, tim.peters
Date 2016-07-14.08:33:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAH_1eM2+LLnnyGkE9U4WnEKR=JONPofVNMAKHi=U05zTxW=fTQ@mail.gmail.com>
In-reply-to <1468478543.31.0.832170975833.issue18966@psf.upfronthosting.co.za>
Content
One reason for not calling sys.exit() is because on Linux, the default
implementation uses fork(), hence the address space in the chilren is
a clone of the parent: so all atexit handlers, for example, would be
called multiple times.
There's also the problem that fork() isn't MT-safe, making the
probability of screwups/deadlocks in various destructors/stack
unwinding greater.
History
Date User Action Args
2016-07-14 08:33:23neologixsetrecipients: + neologix, tim.peters, pitrou, pietvo, sbt, eryksun, davin
2016-07-14 08:33:23neologixlinkissue18966 messages
2016-07-14 08:33:23neologixcreate