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_
Frédéric Bastien writes:
> Hi,
> mmap can give a speed up in some case, but slow down in other. So care
> must be taken when using it. For example, the speed difference between
> read and mmap are not the same when the file is local and when it is
> on NFS. On NFS, you need to read bigger chunk to
Hi,
mmap can give a speed up in some case, but slow down in other. So care
must be taken when using it. For example, the speed difference between
read and mmap are not the same when the file is local and when it is
on NFS. On NFS, you need to read bigger chunk to make it worthwhile.
Another examp
Le 02/03/2012 14:39, Nathaniel Smith a écrit :
> If/when someone adds __float128 support to numpy we should really just
> call it float128
I agree!
Other types could become "float80_128" and "float80_96", as mentioned
about a week ago by Matthew.
--
Pierre
signature.asc
Description: OpenPGP d
On Mar 2, 2012 10:48 AM, "Paweł Biernat" wrote:
> The portability is broken for numpy.float128 anyway (as I understand,
> it behaves in different ways on different architectures), so adding a
> new type (call it, say, quad128) that properly supports binary128
> shouldn't be a drawback. Later on, w
Charles R Harris gmail.com> writes:
>
>
> The quad precision library has been there for a while, and quad
precision is also supported by the Intel compiler. I don't know
about MSVC. Intel has been working on adding quad precision to their
hardware for several years and there is an IEEE spec
