summaryrefslogtreecommitdiff
path: root/numpy/core/memmap.py
diff options
context:
space:
mode:
authorMatthew Brett <matthew.brett@gmail.com>2008-08-24 20:56:30 +0000
committerMatthew Brett <matthew.brett@gmail.com>2008-08-24 20:56:30 +0000
commit95ab3b5901656dc98711a58231969052165e9017 (patch)
treee0a92dfb57a70aa4978a9a85671de78e6853b647 /numpy/core/memmap.py
parent59034c84a6e9efb605328e37b232f91e3c8c0618 (diff)
downloadnumpy-95ab3b5901656dc98711a58231969052165e9017.tar.gz
Note on mmap size on python 2.5 from numpy book
Diffstat (limited to 'numpy/core/memmap.py')
-rw-r--r--numpy/core/memmap.py8
1 files changed, 8 insertions, 0 deletions
diff --git a/numpy/core/memmap.py b/numpy/core/memmap.py
index 85e424729..05aaefef0 100644
--- a/numpy/core/memmap.py
+++ b/numpy/core/memmap.py
@@ -75,6 +75,14 @@ class memmap(ndarray):
Given a memmap ``fp``, ``isinstance(fp, numpy.ndarray)`` returns
``True``.
+ Notes
+ -----
+
+ Memory-mapped arrays use the the Python memory-map object which
+ (prior to Python 2.5) does not allow files to be larger than a
+ certain size depending on the platform. This size is always < 2GB
+ even on 64-bit systems.
+
Examples
--------
>>> data = np.arange(12, dtype='float32')