Author neologix
Recipients georg.brandl, nedbat, neologix, pitrou
Date 2012-12-31.12:01:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAH_1eM0Mj9YUzzNXOcmnu3kaKwZO_8TJQhtH+1Sf48z62hVHvA@mail.gmail.com>
In-reply-to <1356954375.38.0.0942756878609.issue16822@psf.upfronthosting.co.za>
Content
The first reason for not calling atexit handlers upon exec() is that
it wouldn't be async-safe anymore, and could result in deadlocks.
Also, since atexit handlers are inherited upon fork(), running atexit
handlers upon exec() could result in such handlers being called
several times - something which should definitely be avoided.

Note that the atexit documentation states that handlers will only be
called in case of "normal interpreter termination".

So I'm -1 on the change, the chance of breaking existing applications
is way too high.
History
Date User Action Args
2012-12-31 12:01:03neologixsetrecipients: + neologix, georg.brandl, pitrou, nedbat
2012-12-31 12:01:03neologixlinkissue16822 messages
2012-12-31 12:01:03neologixcreate