summaryrefslogtreecommitdiff
path: root/numpy/core/memmap.py
diff options
context:
space:
mode:
authorJarrod Millman <millman@berkeley.edu>2008-04-20 11:49:35 +0000
committerJarrod Millman <millman@berkeley.edu>2008-04-20 11:49:35 +0000
commit8c663313de36e860bbfea0909de181d330bfdfc7 (patch)
treea7b5f3585d2b8a2d8307bfb03dd0e449fa732860 /numpy/core/memmap.py
parentcb7de97f089b67eaacf37ddbebcfb91c292c0ef4 (diff)
downloadnumpy-8c663313de36e860bbfea0909de181d330bfdfc7.tar.gz
ran reindent in preparation for the 1.1 release
Diffstat (limited to 'numpy/core/memmap.py')
-rw-r--r--numpy/core/memmap.py3
1 files changed, 1 insertions, 2 deletions
diff --git a/numpy/core/memmap.py b/numpy/core/memmap.py
index 93950c5c0..c7705d263 100644
--- a/numpy/core/memmap.py
+++ b/numpy/core/memmap.py
@@ -20,7 +20,7 @@ class memmap(ndarray):
Memory-mapped files are used for accessing small segments of large files
on disk, without reading the entire file into memory. Numpy's memmaps are
- array-like objects. This differs from python's mmap module which are
+ array-like objects. This differs from python's mmap module which are
file-like objects.
Parameters
@@ -250,4 +250,3 @@ class memmap(ndarray):
# flush any changes to disk, even if it's a view
self.flush()
self._close()
-