John Nagle <na...@animats.com> writes: >> However, things have changed, and lists and tuple *are* effectively >> mutable and hashable versions of each other... > It's the concurrency aspect of this that interests me, though. > A language with immutable objects can potentially handle concurrency > more safely than one where everything is potentially mutable. > The language knows what can't change, which simplifies locking.
I wonder how well that applies to tuples containing mutable objects, e.g. t = ([1,2], [3,4]) -- http://mail.python.org/mailman/listinfo/python-list
