2011/9/30 Mark Wiebe
> On Fri, Sep 23, 2011 at 1:52 PM, Olivier Delalleau wrote:
>
>> NB: I opened a ticket (http://projects.scipy.org/numpy/ticket/1949) about
>> this, in case it would help getting some attention on this issue.
>>
>
> A lot of what you're seeing here is due to changes I did for
On Fri, Sep 23, 2011 at 1:52 PM, Olivier Delalleau wrote:
> NB: I opened a ticket (http://projects.scipy.org/numpy/ticket/1949) about
> this, in case it would help getting some attention on this issue.
>
A lot of what you're seeing here is due to changes I did for 1.6. I
generally made the casti
NB: I opened a ticket (http://projects.scipy.org/numpy/ticket/1949) about
this, in case it would help getting some attention on this issue.
Besides this, I've been experimenting with the cast mechanisms of mixed
scalar / array operations in numpy 1.6.1 on a Linux x86_64 architecture, and
I can't m
2011/8/8 Charles R Harris
>
>
> On Mon, Aug 8, 2011 at 10:54 AM, Olivier Delalleau wrote:
>
>> Hi,
>>
>> This is with numpy 1.6.1 under Linux x86_64, testing the upcast mechanism
>> of "scalar + array":
>>
>> >>> import numpy; print (numpy.array(3, dtype=numpy.complex128) +
>> numpy.ones(3, dtyp
On Mon, Aug 8, 2011 at 10:54 AM, Olivier Delalleau wrote:
> Hi,
>
> This is with numpy 1.6.1 under Linux x86_64, testing the upcast mechanism
> of "scalar + array":
>
> >>> import numpy; print (numpy.array(3, dtype=numpy.complex128) +
> numpy.ones(3, dtype=numpy.float32)).dtype
> complex64
>
> Si
Hi,
This is with numpy 1.6.1 under Linux x86_64, testing the upcast mechanism of
"scalar + array":
>>> import numpy; print (numpy.array(3, dtype=numpy.complex128) +
numpy.ones(3, dtype=numpy.float32)).dtype
complex64
Since it has to upcast my array (float32 is not "compatible enough" with
comple
