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 jcea
Recipients jcea
Date 2013-08-23.04:55:08
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Currently, "mmap.flush()" does a synchronous write to the backend file. The call will wait until data is actually flushed to disk, because internally it is doing a "msync(MS_SYNC)".

But the value of "mmap.flush()" is to synchronize file and memory. You don't need a synchronous write in the general case.

I propose to add an optional keyword parameter with default value "SYNC" (compatibility) but that can be "ASYNC", "INVALIDATE" (can be "SYNC|INVALIDATE" and "ASYNC|INVALIDATE" too).

I am talking about UNIX MMAP. No idea about Windows.

Check "man msync" for useful cases.
Date User Action Args
2013-08-23 04:55:08jceasetrecipients: + jcea
2013-08-23 04:55:08jceasetmessageid: <>
2013-08-23 04:55:08jcealinkissue18816 messages
2013-08-23 04:55:08jceacreate