diff options
| author | Tom Bird <tombird1992@gmail.com> | 2016-08-17 14:50:28 +0100 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2016-08-17 14:50:28 +0100 |
| commit | 0b38e3bae4747d0691cf3bbf0969cf76d9f5a478 (patch) | |
| tree | 9a10d45c4ada2df71d2ad3c290a5363f7d504b5d /numpy/core/memmap.py | |
| parent | 630917f4e9dd432da1733fceff0c7c455973fa70 (diff) | |
| download | numpy-0b38e3bae4747d0691cf3bbf0969cf76d9f5a478.tar.gz | |
DOC: #7927. Remove deprecated note for memmap relevant for Python <2.5
Diffstat (limited to 'numpy/core/memmap.py')
| -rw-r--r-- | numpy/core/memmap.py | 5 |
1 files changed, 0 insertions, 5 deletions
diff --git a/numpy/core/memmap.py b/numpy/core/memmap.py index 5f6182742..0945b1748 100644 --- a/numpy/core/memmap.py +++ b/numpy/core/memmap.py @@ -103,11 +103,6 @@ class memmap(ndarray): Given a memmap ``fp``, ``isinstance(fp, numpy.ndarray)`` returns ``True``. - Memory-mapped arrays use 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. - When a memmap causes a file to be created or extended beyond its current size in the filesystem, the contents of the new part are unspecified. On systems with POSIX filesystem semantics, the extended |