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

Charles-Francois Natali report at bugs.python.org
Sun Jan 9 00:28:25 CET 2011


Charles-Francois Natali <neologix at 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 http://svn.python.org/view/python/branches/py3k/Modules/mmapmodule.c?r1=84950&r2=85678

Note that you shouldn't be calling flush in the first place...

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue10867>
_______________________________________


More information about the Python-bugs-list mailing list