Adam Olsen wrote: > Less confusing to prohibit concatenation of mismatched types. There's > always trivial workarounds (ie () + tuple([]) or .extend()).
Normally I would agree, but in this case I feel that it would be inconvenient. With the scheme I proposed, code that treats bytes as read-only doesn't have to care whether it has a mutable or immutable object. If they were as rigidly separated as lists and tuples, every API would have to be strictly aware of whether it dealt with mutable or immutable bytes. I could be wrong, though. It may turn out that keeping them separate is the right thing to do. -- Greg _______________________________________________ Python-3000 mailing list [email protected] http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
