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 meador.inge
Recipients benjamin.peterson, eric.araujo, giampaolo.rodola, meador.inge, pitrou, skip.montanaro
Date 2010-09-12.18:49:35
SpamBayes Score 0.0012914117
Marked as misclassified No
Message-id <1284317378.12.0.57246342785.issue9788@psf.upfronthosting.co.za>
In-reply-to
Content
I agree with Antoine's LIFO comment.  Also, FWIW, the C standard library behaves in a LIFO manner as well (C99 spec - 7.20.4.3 clause 3):

"First, all functions registered by the atexit function are called, in the reverse order of their registration,253) except that a function is called after any previously registered functions that had already been called at the time it was registered. If, during the call to any such function, a call to the longjmp function is made that would terminate the call to the registered function, the behavior is undefined."
History
Date User Action Args
2010-09-12 18:49:38meador.ingesetrecipients: + meador.inge, skip.montanaro, pitrou, giampaolo.rodola, benjamin.peterson, eric.araujo
2010-09-12 18:49:38meador.ingesetmessageid: <1284317378.12.0.57246342785.issue9788@psf.upfronthosting.co.za>
2010-09-12 18:49:36meador.ingelinkissue9788 messages
2010-09-12 18:49:35meador.ingecreate