Message 308412 - 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	nascheme
Recipients	martin.panter, nascheme, neologix, nikratio, pitrou, serhiy.storchaka, tim.peters, vstinner, xgdomingo
Date	2017-12-15.17:22:11
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<[email protected]>
In-reply-to

Content
In the process of trying to write a test for this, I now realize that PR 4847 is not really a fix. If the underlying file gets closed during an earlier gc.collect() and not during shutdown, the extra flushing step is not going to help. So, using atexit is not really a fix. Maybe there is something else we can do, need to think about it more.

In the process of trying to write a test for this, I now realize that PR 4847 is not really a fix.  If the underlying file gets closed during an earlier gc.collect() and not during shutdown, the extra flushing step is not going to help.  So, using atexit is not really a fix.  Maybe there is something else we can do, need to think about it more.

History
Date	User	Action	Args
2017-12-15 17:22:11	nascheme	set	recipients: + nascheme, tim.peters, pitrou, vstinner, nikratio, neologix, martin.panter, serhiy.storchaka, xgdomingo
2017-12-15 17:22:11	nascheme	set	messageid: <[email protected]>
2017-12-15 17:22:11	nascheme	link	issue17852 messages
2017-12-15 17:22:11	nascheme	create