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 r.david.murray
Recipients Arfrever, barry, eli.bendersky, eric.araujo, eric.smith, ethan.furman, mrabarnett, pitrou, r.david.murray, rhettinger, sbt, serhiy.storchaka, theller, tim.peters, vstinner
Date 2013-09-12.15:02:38
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1378998159.21.0.983330087002.issue18986@psf.upfronthosting.co.za>
In-reply-to
Content
You are conceptualizing this very differently.  In our view, this data structure is for cases where the original key is the most important piece of information (about the keys).  The transformation in the lookup process is entirely in the service of looking up the value paired with that original key when there is more than one possible representation of that key.  It is the original key that is critical when re-serializing the data or otherwise making use of the keys for anything other than lookup.  So this is about making the data structure succinctly model the problem domain, which is what OO is supposed to be good at :)
History
Date User Action Args
2013-09-12 15:02:39r.david.murraysetrecipients: + r.david.murray, tim.peters, barry, theller, rhettinger, pitrou, vstinner, eric.smith, eric.araujo, mrabarnett, Arfrever, eli.bendersky, ethan.furman, sbt, serhiy.storchaka
2013-09-12 15:02:39r.david.murraysetmessageid: <1378998159.21.0.983330087002.issue18986@psf.upfronthosting.co.za>
2013-09-12 15:02:39r.david.murraylinkissue18986 messages
2013-09-12 15:02:38r.david.murraycreate