Hirokazu Yamamoto <ocean-c...@m2.ccsnet.ne.jp> added the comment: > I don't know what mf.read(-1) should do I'm not sure neither.
I think the problem is that mmap uses size_t as length, but uses Py_ssize_t for PyArg_ParseTuple. (PyArg_ParseTuple doesn't support size_t) I think this discrepancy should be fixed. If mmap should use size_t because it should cover all possible memory region which size_t can represent but Py_ssize_t cannot, maybe should PyArg_ParseTuple support size_t? ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue6344> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
