On Sat, May 7, 2011 at 12:00 AM, DJ Luscher wrote:
> Pearu Peterson gmail.com> writes:
> >
> > On Fri, May 6, 2011 at 10:18 PM, DJ Luscher lanl.gov> wrote:
> >
> > I have encountered another minor hangup. For assumed-shape array-valued
> > functions defined within a fortran module there seems
Pearu Peterson gmail.com> writes:
>
> On Fri, May 6, 2011 at 10:18 PM, DJ Luscher lanl.gov> wrote:
>
> I have encountered another minor hangup. For assumed-shape array-valued
> functions defined within a fortran module there seems to be some trouble in
> the autogenerated subroutine wrapper in
On Fri, May 6, 2011 at 10:18 PM, DJ Luscher wrote:
>
> I have encountered another minor hangup. For assumed-shape array-valued
> functions defined within a fortran module there seems to be some trouble in
> the
> autogenerated subroutine wrapper interface. I think it has to do with the
> order
Pearu Peterson gmail.com> writes:
>
> On Fri, May 6, 2011 at 5:55 PM, DJ Luscher lanl.gov> wrote:
> Pearu Peterson gmail.com> writes:
> >
> >
> > Thanks for the bug report!These issues are now fixed
in: https://github.com/numpy/numpy/commit/f393b604 Ralf, feel free to apply
this
> changeset t
On Fri, 06 May 2011 10:06:20 -0700, Nathaniel Smith wrote:
> On Fri, May 6, 2011 at 3:04 AM, Pauli Virtanen wrote:
>> It's terminating with SIGILL, which means that Ubuntu no longer ships a
>> precompiled version of Atlas usable on machines without SSE3.
>
> Yes, that's right.
>
> BTW, where'd y
On Fri, May 6, 2011 at 5:55 PM, DJ Luscher wrote:
> Pearu Peterson gmail.com> writes:
> >
> >
> > Thanks for the bug report!These issues are now fixed in:
> https://github.com/numpy/numpy/commit/f393b604 Ralf, feel free to apply
> this
> changeset to 1.6.x branch if appropriate.Regards,Pearu
>
On Fri, May 6, 2011 at 3:04 AM, Pauli Virtanen wrote:
> It's terminating with SIGILL, which means that Ubuntu no longer ships
> a precompiled version of Atlas usable on machines without SSE3.
Yes, that's right.
BTW, where'd you get that neat detect_cpu_extensions program?
-- Nathaniel
_
Hi,
discovered another small bug. Windows 7 32 bit, Python 2.6.
In [1]: np.__version__
Out[1]: '1.5.1'
In [2]: a=np.zeros((0,2))
In [3]: np.linalg.qr(a)
** On entry to DGEQRF parameter number 4 had an illegal value
--Here python is crashed.
While np.linalg.lstsq doesn't crashs, the error mes
Pearu Peterson gmail.com> writes:
>
>
> Thanks for the bug report!These issues are now fixed in:
https://github.com/numpy/numpy/commit/f393b604 Ralf, feel free to apply this
changeset to 1.6.x branch if appropriate.Regards,Pearu
>
Excellent! Thank you.
I'll cautiously add another concern
On 6 May 2011, at 07:53, Ralf Gommers wrote:
>
> >> Looks okay, and I agree that it's better to fix it now. The timing
> >> is a bit unfortunate though, just after RC2. I'll have closer look
> >> tomorrow and if it can go in, probably tag RC3.
> >>
> >> If in the meantime a few more people could
Thu, 05 May 2011 17:41:35 -0700, Nathaniel Smith wrote:
> Probably just another standard "your BLAS is compiled wrong!" bug, but
> in this case I'm seeing it with the stock versions of ATLAS, numpy, etc.
> included in the latest Ubuntu release (11.04 Natty Narwhal):
> https://bugs.launchpad.net/u
11 matches
Mail list logo
