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 arigo
Recipients arigo, neologix, nikratio, pitrou, serhiy.storchaka, tim.peters, vstinner
Date 2014-12-04.12:53:14
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1417697594.93.0.502203896089.issue17852@psf.upfronthosting.co.za>
In-reply-to
Content
Antoine: sorry if I wasn't clear enough.  Obviously you want to encourage people to close their files, but I think personally that it is very bad for the implementation to *most of the time* work anyway and only rarely fail to flush the files.  So, speaking only about the implementation, it is (imho) a bad idea to rely on finalizers to flush the files, and something else should be done.

Victor: it does not sound complicated to me to keep the BufferedWriter objects in a doubly-chained list.  You're overthinking the issue: there are no multithread issue (we have a GIL) and you don't have to keep track of all 3 objects created by "open".
History
Date User Action Args
2014-12-04 12:53:14arigosetrecipients: + arigo, tim.peters, pitrou, vstinner, nikratio, neologix, serhiy.storchaka
2014-12-04 12:53:14arigosetmessageid: <1417697594.93.0.502203896089.issue17852@psf.upfronthosting.co.za>
2014-12-04 12:53:14arigolinkissue17852 messages
2014-12-04 12:53:14arigocreate