summaryrefslogtreecommitdiff
path: root/numpy/lib/format.py
diff options
context:
space:
mode:
authorRobert Kern <robert.kern@gmail.com>2008-02-27 23:00:48 +0000
committerRobert Kern <robert.kern@gmail.com>2008-02-27 23:00:48 +0000
commit4bff07720759c611331b43fb988e576e0b68cebb (patch)
tree8b398cb1df74ae7b986d7d874b94f57faa94e3ca /numpy/lib/format.py
parenta5615d4917a25331e008959c55cb5de16b7d164c (diff)
downloadnumpy-4bff07720759c611331b43fb988e576e0b68cebb.tar.gz
One dtype representation issue got fixed. Documented the remaining one.
Diffstat (limited to 'numpy/lib/format.py')
-rw-r--r--numpy/lib/format.py13
1 files changed, 7 insertions, 6 deletions
diff --git a/numpy/lib/format.py b/numpy/lib/format.py
index 99a6b0ed1..c328e0ddb 100644
--- a/numpy/lib/format.py
+++ b/numpy/lib/format.py
@@ -1,12 +1,13 @@
""" Define a simple format for saving numpy arrays to disk with the full
information about them.
-WARNING: Due to limitations in the string representation of dtypes, some
-complicated nested structures will not be faithfully recorded in the file. We
-are working on a fix for this. This fix will not require a change in the file
-format. The arrays with complicated structures can still be saved, but the
-correct dtype will have to be restored by using the
-`loadedarray.view(correct_dtype)` method.
+WARNING: Due to limitations in the interpretation of structured dtypes, dtypes
+with fields with empty names will have the names replaced by 'f0', 'f1', etc.
+Such arrays will not round-trip through the format entirely accurately. The data
+is intact; only the field names will differ. We are working on a fix for this.
+This fix will not require a change in the file format. The arrays with such
+structures can still be saved and restored, and the correct dtype may be
+restored by using the `loadedarray.view(correct_dtype)` method.
Format Version 1.0
------------------