Stefan Krah added the comment: Thanks, #12845 is indeed fixed in NumPy.
Why does NumPy consider an array with a stride that will almost certainly lead to undefined behavior (unless you compile with -fwrapv) as valid? In CPython we try to eliminate these kinds of issues (though they may still be present). >>> import numpy as np import io x = np.arange(10) y = np.array([x]) print(y.strides) (9223372036854775807, 8) >>> >>> >>> y.flags C_CONTIGUOUS : True F_CONTIGUOUS : True OWNDATA : True WRITEABLE : True ALIGNED : True UPDATEIFCOPY : False ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue22445> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
