On Tue, Mar 6, 2012 at 6:53 AM, Matthew Brett wrote:
> Hi,
>
> On Mon, Mar 5, 2012 at 8:04 PM, Mark Wiebe wrote:
> > I've pushed a bugfix to github, can you confirm that the crash goes away
> on
> > your test box? Thanks for tracking that down, the stack trace was very
> > helpful. Since x86 mach
Hi,
On Mon, Mar 5, 2012 at 8:04 PM, Mark Wiebe wrote:
> I've pushed a bugfix to github, can you confirm that the crash goes away on
> your test box? Thanks for tracking that down, the stack trace was very
> helpful. Since x86 machines don't have as strict alignment requirements,
> bugs like this
I've pushed a bugfix to github, can you confirm that the crash goes away on
your test box? Thanks for tracking that down, the stack trace was very
helpful. Since x86 machines don't have as strict alignment requirements,
bugs like this one will generally remain undetected until someone tests on
an a
I'm not sure if it's been re-hashed again or not, but this is the sort of error
that showed up all the time while debugging NumPy on Sparc hard-ware. The
problem is that memory has to be aligned before calculations take place.
With this kind of dtype, field 'f2' will be aligned on a 2-byte
And simplifying:
In [1]: import numpy as np
In [2]: control = np.array([(1, 2, 3), (0, 5, 6)], dtype=[('f0',
bool), ('f1', bool), ('f2', int)])
In [3]: control == control
Out[3]: array([ True, True], dtype=bool)
In [4]: from numpy import ma
In [5]: control = ma.array([(1, 2, 3), (0, 5, 6)], d
Hi,
On Mon, Mar 5, 2012 at 11:11 AM, Matthew Brett wrote:
> Hi,
>
> On Sun, Mar 4, 2012 at 11:53 PM, Mark Wiebe wrote:
>> On Sun, Mar 4, 2012 at 10:34 PM, Matthew Brett
>> wrote:
>>>
>>>
>>> > $ export NPY_SEPARATE_COMPILATION=1
>>>
>>> Thanks, that did it:
>>>
>>> 9194b3af704df71aa9b1ff2f53f1
Hi,
On Sun, Mar 4, 2012 at 11:53 PM, Mark Wiebe wrote:
> On Sun, Mar 4, 2012 at 10:34 PM, Matthew Brett
> wrote:
>>
>>
>> > $ export NPY_SEPARATE_COMPILATION=1
>>
>> Thanks, that did it:
>>
>> 9194b3af704df71aa9b1ff2f53f169848d0f9dc7 is the first bad commit
>>
>> Let me know if I can debug furt
On Mon, Mar 5, 2012 at 1:20 AM, Travis Oliphant wrote:
>
> The place this is used inside of setup.py is here:
>
> https://github.com/numpy/numpy/blob/master/numpy/core/setup.py#L14
>
> I really dislike this build feature, it repeatedly trips me up. In my
> opinion, the build should be changed to
>
> The place this is used inside of setup.py is here:
>
> https://github.com/numpy/numpy/blob/master/numpy/core/setup.py#L14
>
> I really dislike this build feature, it repeatedly trips me up. In my
> opinion, the build should be changed to always do separate compilation, and
> the single fil
On Sun, Mar 4, 2012 at 10:34 PM, Matthew Brett wrote:
>
> > $ export NPY_SEPARATE_COMPILATION=1
>
> Thanks, that did it:
>
> 9194b3af704df71aa9b1ff2f53f169848d0f9dc7 is the first bad commit
>
> Let me know if I can debug further,
>
That commit was a rewrite of np.concatenate, and I've traced the
Hi,
On Sun, Mar 4, 2012 at 8:32 PM, Mark Wiebe wrote:
> On Sun, Mar 4, 2012 at 10:08 PM, Matthew Brett
> wrote:
>>
>> Hi,
>>
>> On Sun, Mar 4, 2012 at 11:41 AM, Mark Wiebe wrote:
>> > On Sun, Mar 4, 2012 at 11:27 AM, Matthew Brett
>> > wrote:
>> >>
>> >> Hi,
>> >>
>> >> On Sat, Mar 3, 2012 at
On Sun, Mar 4, 2012 at 10:08 PM, Matthew Brett wrote:
> Hi,
>
> On Sun, Mar 4, 2012 at 11:41 AM, Mark Wiebe wrote:
> > On Sun, Mar 4, 2012 at 11:27 AM, Matthew Brett
> > wrote:
> >>
> >> Hi,
> >>
> >> On Sat, Mar 3, 2012 at 12:07 AM, Matthew Brett >
> >> wrote:
> >> > Hi,
> >> >
> >> > On Fri,
Hi,
On Sun, Mar 4, 2012 at 11:41 AM, Mark Wiebe wrote:
> On Sun, Mar 4, 2012 at 11:27 AM, Matthew Brett
> wrote:
>>
>> Hi,
>>
>> On Sat, Mar 3, 2012 at 12:07 AM, Matthew Brett
>> wrote:
>> > Hi,
>> >
>> > On Fri, Mar 2, 2012 at 9:05 PM, Charles R Harris
>> > wrote:
>> >>
>> >>
>> >> On Fri, Ma
On Sun, Mar 4, 2012 at 12:27 PM, Matthew Brett wrote:
> Hi,
>
> On Sat, Mar 3, 2012 at 12:07 AM, Matthew Brett
> wrote:
> > Hi,
> >
> > On Fri, Mar 2, 2012 at 9:05 PM, Charles R Harris
> > wrote:
> >>
> >>
> >> On Fri, Mar 2, 2012 at 4:36 PM, Matthew Brett
> >> wrote:
> >>>
> >>> Hi,
> >>>
> >>
On Sun, Mar 4, 2012 at 11:27 AM, Matthew Brett wrote:
> Hi,
>
> On Sat, Mar 3, 2012 at 12:07 AM, Matthew Brett
> wrote:
> > Hi,
> >
> > On Fri, Mar 2, 2012 at 9:05 PM, Charles R Harris
> > wrote:
> >>
> >>
> >> On Fri, Mar 2, 2012 at 4:36 PM, Matthew Brett
> >> wrote:
> >>>
> >>> Hi,
> >>>
> >>
Hi,
On Sat, Mar 3, 2012 at 12:07 AM, Matthew Brett wrote:
> Hi,
>
> On Fri, Mar 2, 2012 at 9:05 PM, Charles R Harris
> wrote:
>>
>>
>> On Fri, Mar 2, 2012 at 4:36 PM, Matthew Brett
>> wrote:
>>>
>>> Hi,
>>>
>>> Sorry that this report is not complete, I don't have full access to
>>> this box but
Hi,
On Fri, Mar 2, 2012 at 9:05 PM, Charles R Harris
wrote:
>
>
> On Fri, Mar 2, 2012 at 4:36 PM, Matthew Brett
> wrote:
>>
>> Hi,
>>
>> Sorry that this report is not complete, I don't have full access to
>> this box but, on a Debian squeeze machine running linux
>> 2.6.32-5-sparc64-smp:
>>
>> n
On Fri, Mar 2, 2012 at 4:36 PM, Matthew Brett wrote:
> Hi,
>
> Sorry that this report is not complete, I don't have full access to
> this box but, on a Debian squeeze machine running linux
> 2.6.32-5-sparc64-smp:
>
> nosetests
> ~/usr/local/lib/python2.6/site-packages/numpy/lib/tests/test_io.py:Te
Hi,
Sorry that this report is not complete, I don't have full access to
this box but, on a Debian squeeze machine running linux
2.6.32-5-sparc64-smp:
nosetests
~/usr/local/lib/python2.6/site-packages/numpy/lib/tests/test_io.py:TestFromTxt.test_user_missing_values
test_user_missing_values (test_
19 matches
Mail list logo
