This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author zzzeek
Recipients alexandre.vassalotti, belopolsky, eric.araujo, grubert, rhettinger, schmir, zzzeek
Date 2010-07-16.00:26:35
SpamBayes Score 0.0005933992
Marked as misclassified No
Message-id <>
where is it defined that sets are not "supposed" to contain mutable items?   such a requirement vastly limits the usefulness of sets.

Consider that relational database rows are mutable.  A result set containing multiple rows which each have a primary key comprises a set, hashed on primary key.  But other attributes of each row can be updated.   Surely this is not controversial ?  What Python data structure should I (and a whole bunch of Python ORMs) be using to represent mutable, relational database rows, unordered and unique on primary key, in memory ?
Date User Action Args
2010-07-16 00:26:40zzzeeksetrecipients: + zzzeek, rhettinger, belopolsky, grubert, alexandre.vassalotti, schmir, eric.araujo
2010-07-16 00:26:39zzzeeksetmessageid: <>
2010-07-16 00:26:37zzzeeklinkissue9269 messages
2010-07-16 00:26:36zzzeekcreate