[issue10867] mmap.flush() issue msync() even if mapping was created with prot=mmap.PROT_READ only

2011-02-20 Thread Марк Коренберг
Changes by Марк Коренберг socketp...@gmail.com: -- resolution: - duplicate status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue10867 ___

[issue10867] mmap.flush() issue msync() even if mapping was created with prot=mmap.PROT_READ only

2011-01-08 Thread Марк Коренберг
Марк Коренберг socketp...@gmail.com added the comment: I have changed title of the bug. This is more precisely describe the problem. In my code, I do mmap.close(), so msync does not called. Generally, calling msync() on read-only mapping is not needed at all. And meven more, calling msync()

[issue10867] mmap.flush() issue msync() even if mapping was created with prot=mmap.PROT_READ only

2011-01-08 Thread Charles-Francois Natali
Charles-Francois Natali neolo...@free.fr added the comment: have changed title of the bug. This is more precisely describe the problem Yes, its's not quite the same problem. I think, that flush() should be no-op if mapping is read-only. This has already be done for py3k. See