Closed jturner314 closed 2 months ago
As @jonathanstrong pointed out in #46, NumPy and ndarray-npy currently behave differently regarding the names of the arrays in .npz files. When writing a .npz file, NumPy unconditionally adds ".npy" to every name. When generating the public list of names when reading a .npz file, NumPy strips a single ".npy" (if present) from each name. When accessing an array in a .npz file by name, it first checks if that exact name is in the .npz file, and if not, it then tries the name with ".npy" appended. While I personally dislike the inconsistency/implicitness of this behavior, ndarray-npy should consider following it for compatibility with NumPy.
ndarray-npy
.npz
As @jonathanstrong pointed out in #46, NumPy and
ndarray-npycurrently behave differently regarding the names of the arrays in.npzfiles. When writing a.npzfile, NumPy unconditionally adds ".npy" to every name. When generating the public list of names when reading a.npzfile, NumPy strips a single ".npy" (if present) from each name. When accessing an array in a.npzfile by name, it first checks if that exact name is in the.npzfile, and if not, it then tries the name with ".npy" appended. While I personally dislike the inconsistency/implicitness of this behavior,ndarray-npyshould consider following it for compatibility with NumPy.