➜

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 neologix
Recipients neologix, socketpair
Date 2011-01-08.16:02:47
SpamBayes Score 0.0003230412
Marked as misclassified No
Message-id <1294502572.57.0.589484247611.issue10867@psf.upfronthosting.co.za>
In-reply-to
Content 
> 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.

The patch (one line) might be worth backporting, though.
History
Date User Action Args
2011-01-08 16:02:52neologixsetrecipients: + neologix, socketpair
2011-01-08 16:02:52neologixsetmessageid: <1294502572.57.0.589484247611.issue10867@psf.upfronthosting.co.za>
2011-01-08 16:02:47neologixlinkissue10867 messages
2011-01-08 16:02:47neologixcreate