At some point during pyres_worker startup, the Python PRNG is
seeded. Since pyres_worker doesn't generate any random numbers on
its own, each job process that is forked starts with the PRNG in
the same state, and they share the same sequence of random numbers.
At some point during pyres_worker startup, the Python PRNG is seeded. Since pyres_worker doesn't generate any random numbers on its own, each job process that is forked starts with the PRNG in the same state, and they share the same sequence of random numbers.
Fixes #82 https://github.com/binarydud/pyres/issues/82