[Numpy-discussion] BUG!

[Bruce Southey]

Hi,
This appears to occur in numarray (1.3.3) but not Numeric (24.0b2). If you
provide the shape of the array then this does not occur.

Also, please note that your other email illustrates the well known problem
of using computer clock as a seed - the computer clock does not change
sufficiently fast enough so the seed remains the same.

Regards
Bruce



On 11/10/05, Sune Rastad Bahn <bahn at atomistix.com > wrote:
>
> Dear devs,
>
> Thanks a lot for a very nice and extremely useful python module.
> I recommend all my colleagues to try you package whenever they ask for a
> matlab like environment. This week one of these friends came by me and
> showed
> me a bug in RandomArray.
>
> try the following
>
> python -c "from RandomArray import *;
> seed(1874764637, 1152239787);print randint(0,1000)"
>
> and notice how the result is the upper limit (1000)
> even though the documentation clearly states that the number should be
> strictly below 1000.
>
> My guess is that this is an issue with the underlying ranlib library, but
> perhaps someone can clarify?
>
> best,
> Sune
>
> --
> Software Application Manager
> Sune Rastad Bahn
> Phone: +45 35 320 638
> Mobile: +45 23 455 997
> Email: bahn at atomistix.com
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by:
> Tame your development challenges with Apache's Geronimo App Server.
> Download
> it for free - -and be entered to win a 42" plasma tv or your very own
> Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
> _______________________________________________
> Numpy-discussion mailing list
> Numpy-discussion at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/numpy-discussion
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20051110/14579eb7/attachment-0001.html>