Sebastian Berg added the comment: Numpy 1.9. was only released recently, so 1.10. might be a while. If no problems show up during release or until then, we will likely switch it by then. But that could end up being a year from now, so I am not sure if 3.6 might not fit better. The problems should be mostly mitigated on our side. So bug-wise it shouldn't be a big issue I would guess.
I will try to look at it more soon, but am completly overloaded at least for the next few days, and maybe some other numpy devs can chip in. Not sure I get your last point, slicing should give the "organic" values even for the mangled up thing with relaxed strides on (currently)?! ---------- _______________________________________ 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
