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 nikratio
Recipients arigo, neologix, nikratio, serhiy.storchaka, tim.peters, vstinner
Date 2014-12-04.18:23:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1417717429.37.0.398187494335.issue17852@psf.upfronthosting.co.za>
In-reply-to
Content
This will probably be too radial, but I think it should at least be mentioned as a possible option.
 
We could just not attempt to implicitly flush buffers in the finalizer at all. This means scripts relying on this will break, but in contrast to the current behavior they will break consistently so it's easy to find and fix the problem.

I think this is still preferable to any solution that does not guarantee flushing in 100% of the cases.
History
Date User Action Args
2014-12-04 18:23:49nikratiosetrecipients: + nikratio, tim.peters, arigo, vstinner, neologix, serhiy.storchaka
2014-12-04 18:23:49nikratiosetmessageid: <1417717429.37.0.398187494335.issue17852@psf.upfronthosting.co.za>
2014-12-04 18:23:49nikratiolinkissue17852 messages
2014-12-04 18:23:49nikratiocreate