Hi Bruce,
I think we have some fundamental misunderstandings about what this
proposal would do. Let me see if I can try to be clearer.
On Sun, Jul 10, 2011 at 7:33 PM, Bruce Southey wrote:
> On Fri, Jul 8, 2011 at 5:04 PM, Nathaniel Smith wrote:
>> Each dtype has a bunch of C functions associat
On Sun, Jul 10, 2011 at 8:26 PM, Roy Lowrance wrote:
> I have a 1D float64 array ts. I want to square each element, so I compute
> x = ts * ts
>
> I get a floating point overflow error.
>
> However, when I access each element separately and multiple, I get no
> error:
> for i in ts.shape[0]:
>
On Fri, Jul 8, 2011 at 4:35 PM, Matthew Brett wrote:
> Hi,
>
> On Fri, Jul 8, 2011 at 8:34 PM, Bruce Southey wrote:
>> On Fri, Jul 8, 2011 at 12:55 PM, Matthew Brett
>> wrote:
>>> Hi,
>>>
>>> On Fri, Jul 8, 2011 at 6:38 PM, Bruce Southey wrote:
On 07/08/2011 08:58 AM, Matthew Brett wrote:
On Fri, Jul 8, 2011 at 5:04 PM, Nathaniel Smith wrote:
> Hi Bruce,
>
> I'm replying on the list instead of on github, to make it easier for
> others to join in the discussion if they want. [For those joining in:
> this was a comment posted at https://gist.github.com/1068264 ]
>
> On Fri, Jul 8, 20
I have a 1D float64 array ts. I want to square each element, so I compute
x = ts * ts
I get a floating point overflow error.
However, when I access each element separately and multiple, I get no error:
for i in ts.shape[0]:
___
NumPy-Discussion mail
Hello,
building numpy 1.6.1rc2 on Windows, i7-2600K CPU, with msvc9 failed with
the following error:
File "numpy/core/setup_common.py", line 271, in long_double_representation
raise ValueError("Could not lock sequences (%s)" % saw)
ValueError: Could not lock sequences (None)
This problem
>From the pull request:
https://github.com/numpy/numpy/pull/108
The two flags NPY_ITER_WRITEMASKED and NPY_ITER_ARRAYMASK now fully work.
This made it easy to fix the ufunc 'where=' bug. Also added documentation of
the new iterator flags and inline functions for dealing with masks.
Special thank
