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 BreamoreBoy
Recipients BreamoreBoy, ajaksu2, loewis, mdr0, nnorwitz, pitrou, sable, tim.peters, wheelrl
Date 2010-09-21.21:58:13
SpamBayes Score 0.000432939
Marked as misclassified No
Message-id <>
In-reply-to <>
Please ensure tha I'm taken off of the email list as I've been banned from 
contributing to Python by Raymond Hettinger

From: Martin v. Löwis <>
Sent: Tue, 21 September, 2010 16:53:27
Subject: [issue678250] test_mmap failling on AIX

Martin v. Löwis <> added the comment:

> Interestingly, the matter was discussed on another issue, #2643. I
> also agree that ideally flush() should become a no-op (only in 3.2,
> since it would break compatibility). But then we should also expose a
> separate sync() method with the current behaviour.

I think you misunderstand. I'm not proposing that flush should become
a noop entirely - only for ACCESS_COPY mappings.


Python tracker <>
File name Uploaded
unnamed BreamoreBoy, 2010-09-21.21:58:13
Date User Action Args
2010-09-21 22:21:05loewisunlinkissue678250 messages
2010-09-21 21:58:14BreamoreBoysetrecipients: + BreamoreBoy, tim.peters, loewis, nnorwitz, wheelrl, mdr0, pitrou, sable, ajaksu2
2010-09-21 21:58:13BreamoreBoylinkissue678250 messages
2010-09-21 21:58:13BreamoreBoycreate