On Wed, Jun 10, 2015 at 7:02 PM, Jaime Fernández del Río < jaime.f...@gmail.com> wrote:
> On Wed, Jun 10, 2015 at 5:53 PM, Jaime Fernández del Río < > jaime.f...@gmail.com> wrote: > >> I'm in the midst of a Python 3.5 + MSVS 2015 compilation frenzy. Today it >> was time for Open CV 3.0, where I found a nasty bug that I have eventually >> tracked down to using a development version of NumPy, and Open CV 3.0 >> choking on relaxed strides, as it does a check that every stride is a >> multiple of the itemsize. >> >> I was thinking of submitting a patch to opencv to fix this, but was >> wondering whether we have plans to eventually have relaxed strides out in >> the wild in user releases, or is it just a testing tool for development? >> > > I see that in the release notes of 1.9 we had the following: > > > - Relaxed stride checking will be the default in 1.10.0 > > Is this still the plan? > Yes, but it won't be quite the same as the master branch. Currently an unusual value for the stride (?) is used in order to smoke out misuse, but that value will be more rational in the release. Chuck
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion
