Writable :term:`bytes-like object` is now accepted.
- .. method:: flush()
- flush(offset, size, /)
+ .. method:: flush([offset[, size]])
Flushes changes made to the in-memory copy of a file back to disk. Without
use of this call there is no guarantee that changes are written back before
on error under Windows. A zero value was returned on success; an
exception was raised on error under Unix.
+ .. versionchanged:: next
+ Allow specifying *offset* without *size*. Previously, both *offset*
+ and *size* parameters were required together. Now *offset* can be
+ specified alone, and the flush operation will extend from *offset*
+ to the end of the mmap.
+
.. method:: madvise(option[, start[, length]])
self.assertEqual(stdout.strip(), b'')
self.assertEqual(stderr.strip(), b'')
+ def test_flush_parameters(self):
+ with open(TESTFN, 'wb+') as f:
+ f.write(b'x' * PAGESIZE * 3)
+ f.flush()
+
+ m = mmap.mmap(f.fileno(), PAGESIZE * 3)
+ self.addCleanup(m.close)
+
+ m.flush()
+ m.flush(PAGESIZE)
+ m.flush(PAGESIZE, PAGESIZE)
+
class LargeMmapTests(unittest.TestCase):
--- /dev/null
+Fixed a bug in :meth:`mmap.mmap.flush` where calling with only an offset
+parameter would fail.
mmap_flush_method(PyObject *op, PyObject *args)
{
Py_ssize_t offset = 0;
+ Py_ssize_t size = -1;
mmap_object *self = mmap_object_CAST(op);
- Py_ssize_t size = self->size;
CHECK_VALID(NULL);
- if (!PyArg_ParseTuple(args, "|nn:flush", &offset, &size))
+ if (!PyArg_ParseTuple(args, "|nn:flush", &offset, &size)) {
return NULL;
+ }
+ if (size == -1) {
+ size = self->size - offset;
+ }
if (size < 0 || offset < 0 || self->size - offset < size) {
PyErr_SetString(PyExc_ValueError, "flush values out of range");
return NULL;