On 3/28/2011 3:42 AM, Esben Nielsen wrote:
Hi,
We are making a prototype program in Python. I discovered the output was
non-deterministic, i.e. I rerun the program on the same input files and
get different output files. We do not use any random calls, nor
threading.
One of us thought it could b
On Mon, 2011-03-28 at 12:58 +0100, Tim Wintle wrote:
> On Mon, 2011-03-28 at 12:42 +0200, Esben Nielsen wrote:
> > We are making a prototype program in Python. I discovered the output was
> > non-deterministic, i.e. I rerun the program on the same input files and
> > get different output files. We
Esben Nielsen wrote:
> Hi,
>
> We are making a prototype program in Python. I discovered the output was
> non-deterministic, i.e. I rerun the program on the same input files and
> get different output files. We do not use any random calls, nor
> threading.
>
> One of us thought it could be set a
On Mon, 2011-03-28 at 12:42 +0200, Esben Nielsen wrote:
> We are making a prototype program in Python. I discovered the output was
> non-deterministic, i.e. I rerun the program on the same input files and
> get different output files. We do not use any random calls, nor
> threading.
>
> One of us
One of us thought it could be set and dictionaries not always yielding
the same results. I, however, would think that given the exact same
operations, a set/dictionary would always yield the same results. Am I
correct? Or could different runs of the same program yield different
results due to, s
