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 berker.peksag
Recipients berker.peksag, byronhawkins, christian.heimes, docs@python, pablogsal, socketpair, xiang.zhang
Date 2018-03-29.00:32:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1522283521.69.0.467229070634.issue32798@psf.upfronthosting.co.za>
In-reply-to
Content
By the way, there is a note in the "Change History" section of the msync() documentation at http://pubs.opengroup.org/onlinepubs/9699919799/

    The second [EINVAL] error condition is made mandatory.

The second EINVAL error condition they mention is:

    [EINVAL] The value of addr is not a multiple of the page size as returned by sysconf().

So unless I'm missing something obvious, the "the msync() function may fail if" part may now be outdated?

Also, I noticed that we don't have tests for mm.flush(offset) and mm.flush(offset, size) cases. It would be nice to add some tests even if we decide to not merge the documentation PR.
History
Date User Action Args
2018-03-29 00:32:01berker.peksagsetrecipients: + berker.peksag, christian.heimes, docs@python, socketpair, xiang.zhang, pablogsal, byronhawkins
2018-03-29 00:32:01berker.peksagsetmessageid: <1522283521.69.0.467229070634.issue32798@psf.upfronthosting.co.za>
2018-03-29 00:32:01berker.peksaglinkissue32798 messages
2018-03-29 00:32:00berker.peksagcreate