> so, still: sorry no, the application should not just look at the result > being returned.
If it doesn't want to lose data, it *has* to, because of the way it's currently implemented. There is no other way (other than ignoring the error) in Python 2.5.x and earlier. > The mmap.flush method should be fixed. I never debated that. I debated whether that is a "rather severe" issue, which I still don't think it is. Regards, Martin _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
