Since mmap objects are said to "behave like both bytearray and like file objects" I believe it's appropriate for the mmap.write() method to return the number of bytes written like write() of other file objects/interfaces I could find in the standard library for consistency reasons:https://docs.python.org/3/library/io.html#io.BufferedIOBase.writehttps://docs.python.org/3/library/io.html#io.BufferedWriter.writehttps://docs.python.org/3/library/io.html#io.RawIOBase.writehttps://docs.python.org/3/library/io.html#io.TextIOBase.writeWhy I believe this would be useful: code that writes to file objects and tests the number of bytes/characters written right now will likely fail when it's passed a mmap object because its write() method returns None. With this patch applied it'll work transparently.Please find proposed patch attached, I included information about the exception type in the documentation as it seems fitting (apologies for generating the patch using Git, I'll generate using Mercurial if necessary).

Thanks for the patch, Jakub. I don't use mmap module much so I don't have an opinion about the feature, but it sounds reasonable.I left some review comments on Rietveld:http://bugs.python.org/review/26335/

Oops, sorry for the silliness in the C code, thanks for reviewing. I modified as suggested, please find the new patch attached.

Patch looks okay to me. I guess it would be good to write a What’s New entry as well.

Thank you. I didn't know whether to add an entry toDoc/whatsnew/3.6.rst,Misc/NEWS or both so I chose both, feel free to modify/remove as needed.The new patch also doesn't have a typo in the versionchanged directive present in the version 2. I noticed more typos like this (single colon instead of double colon), I'll create a separate issue.

New changesetba71aecec943 by Berker Peksag in branch 'default':Issue#26335: Make mmap.write() return the number of bytes written likehttps://hg.python.org/cpython/rev/ba71aecec943

Thanks for the patch, Jakub!

Glad I could help, thanks for merging!