Re: [Cython] "relaxed_strides" test broken with NumPy 1.8

2014-01-04 Thread Nathaniel Smith
No, I'm missing something now; AFAIK there are only two numpy behaviors: with relaxed strides and without relaxed strides, and version number should be irrelevant beyond that. What's different between 1.8-without-relaxed-strides and 1.7 that makes the test break? On 4 Jan 2014 22:01, "Stefan Behnel

Re: [Cython] "relaxed_strides" test broken with NumPy 1.8

2014-01-04 Thread Stefan Behnel
Stefan Behnel, 04.01.2014 22:51: > Stefan Behnel, 04.01.2014 22:47: >> Nathaniel Smith, 04.01.2014 18:36: >>> On 4 Jan 2014 17:07, "Robert Bradshaw" wrote: Yes, that'd be good. Do you know how? I won't have time to look at this >>> 'till next week. >>> >>> Something like >>> >>> if not np.ones

Re: [Cython] "relaxed_strides" test broken with NumPy 1.8

2014-01-04 Thread Stefan Behnel
Stefan Behnel, 04.01.2014 22:47: > Nathaniel Smith, 04.01.2014 18:36: >> On 4 Jan 2014 17:07, "Robert Bradshaw" wrote: >>> Yes, that'd be good. Do you know how? I won't have time to look at this >> 'till next week. >> >> Something like >> >> if not np.ones((10, 1), order="C").flags.f_contiguous: >>

Re: [Cython] "relaxed_strides" test broken with NumPy 1.8

2014-01-04 Thread Stefan Behnel
Nathaniel Smith, 04.01.2014 18:36: > On 4 Jan 2014 17:07, "Robert Bradshaw" wrote: >> Yes, that'd be good. Do you know how? I won't have time to look at this > 'till next week. > > Something like > > if not np.ones((10, 1), order="C").flags.f_contiguous: > # numpy without relaxed stride support

Re: [Cython] "relaxed_strides" test broken with NumPy 1.8

2014-01-04 Thread Nathaniel Smith
On 4 Jan 2014 17:07, "Robert Bradshaw" wrote: > > Yes, that'd be good. Do you know how? I won't have time to look at this 'till next week. Something like if not np.ones((10, 1), order="C").flags.f_contiguous: # numpy without relaxed stride support raise SkipTest > On Jan 4, 2014 9:54 AM, "N

Re: [Cython] "relaxed_strides" test broken with NumPy 1.8

2014-01-04 Thread Robert Bradshaw
Yes, that'd be good. Do you know how? I won't have time to look at this 'till next week. On Jan 4, 2014 9:54 AM, "Nathaniel Smith" wrote: > On 4 Jan 2014 11:53, "Stefan Behnel" wrote: > > > > mark florisson, 03.01.2014 23:28: > > > On 3 January 2014 18:22, Stefan Behnel wrote: > > >> I enabled t

Re: [Cython] "relaxed_strides" test broken with NumPy 1.8

2014-01-04 Thread Nathaniel Smith
On 4 Jan 2014 11:53, "Stefan Behnel" wrote: > > mark florisson, 03.01.2014 23:28: > > On 3 January 2014 18:22, Stefan Behnel wrote: > >> I enabled the NumPy build for our Py3.3 test runs and while I was at it, I > >> got it to use the latest NumPy release 1.8. This made one of the tests fail: > >>

Re: [Cython] "relaxed_strides" test broken with NumPy 1.8

2014-01-04 Thread Stefan Behnel
Robert Bradshaw, 04.01.2014 17:40: > On Sat, Jan 4, 2014 at 6:46 AM, Stefan Behnel wrote: >> Stefan Behnel, 04.01.2014 12:53: >>> I didn't define the NPY_RELAXED_STRIDES_CHECKING >>> environment variable for the NumPy build. Let's try that first. >>> >>> http://docs.scipy.org/doc/numpy/release.html

Re: [Cython] "relaxed_strides" test broken with NumPy 1.8

2014-01-04 Thread Robert Bradshaw
Excellent, thanks. I'll make sure this gets into the release. On Sat, Jan 4, 2014 at 6:46 AM, Stefan Behnel wrote: > Stefan Behnel, 04.01.2014 12:53: >> mark florisson, 03.01.2014 23:28: >>> On 3 January 2014 18:22, Stefan Behnel wrote: I enabled the NumPy build for our Py3.3 test runs and w

Re: [Cython] "relaxed_strides" test broken with NumPy 1.8

2014-01-04 Thread Stefan Behnel
Stefan Behnel, 04.01.2014 12:53: > mark florisson, 03.01.2014 23:28: >> On 3 January 2014 18:22, Stefan Behnel wrote: >>> I enabled the NumPy build for our Py3.3 test runs and while I was at it, I >>> got it to use the latest NumPy release 1.8. This made one of the tests fail: >>> >>> """ >>> T

Re: [Cython] "relaxed_strides" test broken with NumPy 1.8

2014-01-04 Thread Stefan Behnel
mark florisson, 03.01.2014 23:28: > On 3 January 2014 18:22, Stefan Behnel wrote: >> I enabled the NumPy build for our Py3.3 test runs and while I was at it, I >> got it to use the latest NumPy release 1.8. This made one of the tests fail: >> >> """ >> Traceback (most recent call last): >>