Hi,
On Thu, Nov 28, 2013 at 7:14 AM, V S, Nagendra (Nonstop Filesystems Team)
on NonStop uuid.py falls throw to random.range() call to generate the
random number
And indeed, the random module gets identical results in both parent
and child after a fork(). This seems to mean that the random
Am 28.11.2013 10:53, schrieb Armin Rigo:
Hi,
On Thu, Nov 28, 2013 at 7:14 AM, V S, Nagendra (Nonstop Filesystems Team)
on NonStop uuid.py falls throw to random.range() call to generate the
random number
And indeed, the random module gets identical results in both parent
and child after
Hi,
On Thu, Nov 28, 2013 at 7:14 AM, V S, Nagendra (Nonstop Filesystems
Team)
on NonStop uuid.py falls throw to random.range() call to generate
the random number
And indeed, the random module gets identical results in both parent
and child after a fork(). This seems to mean
Hi,
We are porting python to HP NonStop to a large extent we have been
successful. While running the unit tests we happen to hit upon the problem
reported in issue8621(http://bugs.python.org/issue8621), i.e uuid4 sequences on
both parent child were same . On NonStop we lack support for both
