New submission from Марк Коренберг socketp...@gmail.com:
python mmap objects issue msync() in destructor even if mapping was created
with prot=mmap.PROT_READ only
--
messages: 125780
nosy: mmarkk
priority: normal
severity: normal
status: open
title: python mmap objects issue msync()
Марк Коренберг socketp...@gmail.com added the comment:
Soory, this is dup of Issue2643
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10867
___
Марк Коренберг socketp...@gmail.com added the comment:
i'm crazy today. sorry twice. this is not dup of 2643 :(
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue10867
___
Charles-Francois Natali neolo...@free.fr added the comment:
python mmap objects issue msync() in destructor even if mapping was created
with prot=mmap.PROT_READ only
Actually, the call to msync(2) from destructor has been removed altogether in
py3k. See http://bugs.python.org/issue2643.
R. David Murray rdmur...@bitdance.com added the comment:
Antoine didn't want to backport that patch. Does the fix applied in issue
678250 address this?
--
nosy: +r.david.murray
___
Python tracker rep...@bugs.python.org
