> I wasn't suggesting that the result of concatenation would > be a chained table, rather that it would perform the > equivalent of an update and return the new dict >(the same way extend works for lists)
When does it come-up that you want a third summed dict while keeping the two originals around unchanged? Does it matter that the addition is non-commutative? Would a + b + c produce an intermediate a/b combo and then another new object for a/b/c so that the entries in a get copied twice and memory usage has to hold a, b, a/b, c, and a/b/c in memory all at the same time? What are the use cases? FWIW, the Py3.0 API for dicts will support some set-like operations. Perhaps, that fits the bill. Raymond _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
