Tuple assignment and generators?
Diez B. Roggisch
deets at nospam.web.de
Fri May 5 14:27:21 CEST 2006
>> E.g., after "a = 1;
>> b = 1",
>> a and b may or may not refer to the same object with the value one,
>> depending on the implementation,
> But when in a specific implementation this property _does_ hold for
> ints having value 1, I expect the
> same behaviour for ints with other values than 1.
That is an assumption you made. The above sentence is true for that
assumption, but also - and that is the key point here - for the current
And to put it frankly: if you'd had spend only half the time it took you to
participate in this argument to think about how one could possibly
implement the behavior you'd thought of, you'd realize that its totally
unfeasible. Try stuffing 2^64 python long objects in your memory to make
that guarantee hold... And then 2^65
> I guess I'm kind of weird that way.
More information about the Python-list