Tim Hochberg wrote:
> Some time ago some people, myself including, were making some noise
> about having 'array' iterate over iterable object producing ndarrays in
> a manner analogous to they way sequences are treated. I finally got
> around to looking at it seriously and once I came to the fol
Robert Kern schrieb:
>
> My point is that there is no need to change rand() and randn() to the "new"
> interface. The "new" interface is already there: random.random() and
> random.standard_normal().
>
Ok thanks for the responses and sorry for not searching the archives
about this.
I tend to sh
My suggestion would be to have both numpy.org and scipy.org be the
exact same page, but make it extremely clear that there are two
different projects on the front page.
Cheers.
Jon.
On 6/2/06, David M. Cooke <[EMAIL PROTECTED]> wrote:
> On Fri, 2 Jun 2006 10:27:45 +0200
> Joris De Ridder <[EMAIL
Travis Oliphant wrote:
>Tim Hochberg wrote:
>
>
>>Some time ago some people, myself including, were making some noise
>>about having 'array' iterate over iterable object producing ndarrays in
>>a manner analogous to they way sequences are treated. I finally got
>>around to looking at it serio
Hi all,
I just discovered that the diff function returns a numpy-array even for
matrix inputs. Since I'm a card-carrying matrix fanatic, I hope that
behavior qualifies as a bug.
Then I went through some (most?) other functions/methods for which IMO
it's best to return matrices if the input is als
"Boris Borcic" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> after a while trying to find the legal manner to file numpy bug reports,
> since it's a simple one, I thought maybe a first step is to describe the
bug
> here. Then maybe someone will direct me to the right channel.
>
> So
