Sorry for responding to my own post. I think I understand the original statement now. What you are really saying is that there is a pool of Python float objects (which can, at different times, wrap different values) which can grow but never decrease in size. So the memory held by this pool is dictated by the maximum number of floats that have ever been simultaneously active (accessible).
The same goes for integers. All the more reason to avoid range(.) and use xrange(.). So is this correct? Thanks! -- http://mail.python.org/mailman/listinfo/python-list
