Message 164454 - Python tracker

➜

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	georg.brandl
Recipients	docs@python, georg.brandl, loewis, pitrou
Date	2012-07-01.07:58:41
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1341129521.95.0.805489135584.issue15233@psf.upfronthosting.co.za>
In-reply-to

Content
Currently, the atexit docs state "The order in which the functions are called is not defined" in the introduction and "all functions registered are called in last in, first out order" in the docs of the atexit() function. While the latter is correct, I don't think we should guarantee that behaviour by documenting it. Suggestions?

Currently, the atexit docs state

"The order in which the functions are called is not defined" in the introduction and

"all functions registered are called in last in, first out order" in the docs of the atexit() function.

While the latter is correct, I don't think we should guarantee that behaviour by documenting it.  Suggestions?

History
Date	User	Action	Args
2012-07-01 07:58:42	georg.brandl	set	recipients: + georg.brandl, loewis, pitrou, docs@python
2012-07-01 07:58:41	georg.brandl	set	messageid: <1341129521.95.0.805489135584.issue15233@psf.upfronthosting.co.za>
2012-07-01 07:58:41	georg.brandl	link	issue15233 messages
2012-07-01 07:58:41	georg.brandl	create