On Tue, Apr 1, 2008 at 11:56 AM, Andreas Klöckner
<[EMAIL PROTECTED]> wrote:
> Hi all,
>
> is there a particular reason why dot() and tensordot() don't have output
> arguments?
No technical reason. It just hasn't been done. If you were to
implement it, we would be happy to accept it.
--
Robert
Hi all,
is there a particular reason why dot() and tensordot() don't have output
arguments?
Andreas
signature.asc
Description: This is a digitally signed message part.
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy
> For example, it would be nice if "outer"
> supported:
>
> outer(b,c,output=a)
> outer(b,c,increment=a)
> outer(b,c,increment=a,scale=eps)
>
> or maybe one could specify an accumulation ufunc, with addition,
> multiplication, min, and max being fast, and with an optional scale
> parameter.
What
Thomas Breuel wrote:
> Hi,
>
> core NumPy doesn't seem to support a lot of output arguments, or common
> composite operations. For example, a common operation is something like
>
> a = outer(b,c)
>
> or
>
> a += outer(b,c)
>
> There are some workarounds, but they aren't pretty. Consistently
Hi,
core NumPy doesn't seem to support a lot of output arguments, or common
composite operations. For example, a common operation is something like
a = outer(b,c)
or
a += outer(b,c)
There are some workarounds, but they aren't pretty. Consistently providing
output arguments throughout NumPy