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 rhettinger
Recipients belopolsky, loewis, pitrou, r.david.murray, rhettinger, serhiy.storchaka, vstinner
Date 2013-10-10.04:29:05
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1381379345.43.0.881732617288.issue19187@psf.upfronthosting.co.za>
In-reply-to
Content
Based on the discussion so far, I'm going to close this one.  I don't think it is an appropriate use of sets (they are about membership testing, not about looking up values). 

The upside is minimal.  The downside is hacking up the set implementation and making it more difficult to implement some of the other alterations I'm planning for sets -- I want to tune the performance to optimize set operations without worrying about slowing down all the rest of Python because of interned strings.  Martin's reason's for rejecting this previously still hold true.
History
Date User Action Args
2013-10-10 04:29:05rhettingersetrecipients: + rhettinger, loewis, belopolsky, pitrou, vstinner, r.david.murray, serhiy.storchaka
2013-10-10 04:29:05rhettingersetmessageid: <1381379345.43.0.881732617288.issue19187@psf.upfronthosting.co.za>
2013-10-10 04:29:05rhettingerlinkissue19187 messages
2013-10-10 04:29:05rhettingercreate