Why are tuples immutable?
Nick Coghlan
ncoghlan at iinet.net.au
Fri Dec 17 23:26:27 EST 2004
More information about the Python-list mailing list
Fri Dec 17 23:26:27 EST 2004
- Previous message (by thread): Why are tuples immutable?
- Next message (by thread): Why are tuples immutable?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Antoon Pardon wrote: > Would you have us construct two related classes each time we find > ourselves in such a situation and copy an object from one > class to the other depending on the circumstances? Python itself seems to think so, given the pairings of set/frozenset & list/tuple. Using genuinely immutable objects as dictionary keys is much easier than saying "while this object is part of a dictionary, don't alter it's hash value or comparison results". Instead, the immutable version is provided to say "alterations are not allowed on this copy" You can certainly *do* the former (using __hash__ and appropriate comparison overrides), but it isn't particularly easy to do correctly, and hence usually isn't a great idea unless copies are *really* expensive (and even then, a shallow copy approach can often suffice). Cheers, Nick. -- Nick Coghlan | ncoghlan at email.com | Brisbane, Australia --------------------------------------------------------------- http://boredomandlaziness.skystorm.net
- Previous message (by thread): Why are tuples immutable?
- Next message (by thread): Why are tuples immutable?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-list mailing list