diff options
| author | Julian Taylor <juliantaylor108@gmail.com> | 2014-10-12 18:20:29 +0200 |
|---|---|---|
| committer | Julian Taylor <juliantaylor108@gmail.com> | 2014-10-12 18:20:29 +0200 |
| commit | 2ba94e726c7adf5b6ea7f2e49aadb78fe8b1d7ba (patch) | |
| tree | 231a06864c2dbf33f8ebd2fd937875e41be3c42b | |
| parent | 4c4595b2487002162e6ce5e6dd8a9c778e3d7c30 (diff) | |
| parent | ade76b0035496ad0239b5236688fa51d4a4e592e (diff) | |
| download | numpy-2ba94e726c7adf5b6ea7f2e49aadb78fe8b1d7ba.tar.gz | |
Merge pull request #5176 from larsmans/memmap-doc
DOC: core: contents of newly allocated space in memmap
| -rw-r--r-- | numpy/core/memmap.py | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/numpy/core/memmap.py b/numpy/core/memmap.py index b1c96ee29..4b10f361c 100644 --- a/numpy/core/memmap.py +++ b/numpy/core/memmap.py @@ -111,6 +111,11 @@ class memmap(ndarray): 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 + part will be filled with zero bytes. + Examples -------- >>> data = np.arange(12, dtype='float32') |