I was using David Beazley's reference and saw a comment that says it isn't
thread safe, but I must admit that my repro doesn't work for CPython.
anyway, opened codeplex item:
http://www.codeplex.com/IronPython/WorkItem/View.aspx?WorkItemId=18926
On Tue, Oct 14, 2008 at 1:12 AM, Curt Hagenlocher <
The underlying problem in the Python code is likely to be because of the
behavior of the "random" function in the C library. And for us, this is
actually a problem in the BCL. Someone just posted the exact same behavior
to an internal mailing list, but from a C# program. They wrote: "I just
enco
Wow, I'm surprised it's documented as being thread unsafe in CPython, but it's
good to know.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ronnie Maor
Sent: Monday, October 13, 2008 1:57 PM
To: Discussion of IronPython
Subject: Re: [IronPython] Problem with rando
problem was caused by calling random from several threads without locking.
it reproduces more easily in IPy than in CPython because of the GIL, but
it's documented as not thread safe for CPython too.
On Sun, Oct 12, 2008 at 11:27 AM, Asaf Kleinbort <[EMAIL PROTECTED]>wrote:
> Hi,
>
> We have enc
Hi,
We have encountered two strange errors in the 'random' module:
1. At some point the random method 'getrandbits(63)' started (and
kept) returning 0 - until we restarted the application.
2. The random method 'shuffle' when applied on a list kept returning
the same ordered list. Aga
