Antoine Pitrou <pit...@free.fr> added the comment: Oops, sorry: > I don't think this class aims at being safe against concurrent access, > so having it fail loudly is a good thing.
I now understand that the problem is that it doesn't fail loudly. That's what I get for replying too quickly. Still, I don't think the suggested fix is ok. Perhaps we should simply state in the documentation that flush() discards the old file, so that other processes accessing it may get a surprise. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue7360> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
