Re: [Numpy-discussion] Open CV 3.0 + NPY_RELAXED_STRIDES

2015-06-11 Thread Julian Taylor
On Thu, Jun 11, 2015 at 11:39 AM, Sebastian Berg sebast...@sipsolutions.net wrote: On Mi, 2015-06-10 at 21:03 -0600, Charles R Harris wrote: snip * 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

Re: [Numpy-discussion] Open CV 3.0 + NPY_RELAXED_STRIDES

2015-06-11 Thread Sebastian Berg
On Mi, 2015-06-10 at 21:03 -0600, Charles R Harris wrote: snip * 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

Re: [Numpy-discussion] Open CV 3.0 + NPY_RELAXED_STRIDES

2015-06-11 Thread Jaime Fernández del Río
On Thu, Jun 11, 2015 at 2:44 AM, Julian Taylor jtaylor.deb...@googlemail.com wrote: On Thu, Jun 11, 2015 at 11:39 AM, Sebastian Berg sebast...@sipsolutions.net wrote: On Mi, 2015-06-10 at 21:03 -0600, Charles R Harris wrote: snip * Relaxed stride checking will be

Re: [Numpy-discussion] Open CV 3.0 + NPY_RELAXED_STRIDES

2015-06-10 Thread Jaime Fernández del Río
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

Re: [Numpy-discussion] Open CV 3.0 + NPY_RELAXED_STRIDES

2015-06-10 Thread Nathaniel Smith
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