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 loewis
Recipients akuchling, brian.curtin, exarkun, loewis, neologix, pitrou, schmir, trent
Date 2010-09-21.16:00:16
SpamBayes Score 0.00020877723
Marked as misclassified No
Message-id <1285084832.22.0.257925333509.issue2643@psf.upfronthosting.co.za>
In-reply-to
Content
I think Antoine misinterpreted my message. I do think that flush should continue to msync, except in cases where there really is no underlying file to sync to. It may (or may not) be unfortunate that the method is called flush, but nothing is gained by renaming it.

I agree that calling msync on close/dealloc is not really necessary. The Windows version doesn't sync, either.
History
Date User Action Args
2010-09-21 16:00:32loewissetrecipients: + loewis, akuchling, exarkun, pitrou, schmir, trent, brian.curtin, neologix
2010-09-21 16:00:32loewissetmessageid: <1285084832.22.0.257925333509.issue2643@psf.upfronthosting.co.za>
2010-09-21 16:00:16loewislinkissue2643 messages
2010-09-21 16:00:16loewiscreate