Stefan Krah added the comment: FWIW, I think it would be good to make this change early in the 3.5 release cycle, so issues can be found. Sebastian, do you have an idea when the change will be decided in numpy?
Regarding the discussion here ... https://github.com/numpy/numpy/issues/5085 ... about the special stride marker: In the case of slicing it would be nice to use the "organic" value that would arise normally from computing the slice. That helps in checking other PEP-3118 implementations like Modules/_testbuffer.c against numpy. ---------- _______________________________________ 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
