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 zach.ware
Recipients arigo, eric.snow, mark.dickinson, serhiy.storchaka, zach.ware
Date 2013-08-19.20:43:39
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
A lot of this discussion has flown a rather unfortunate distance over my head, especially since I've barely had time to follow it.  But it looks to me like--given the number of other places that do the same thing as operator.index currently does--there needs to be a simple way to do the right thing somewhere accessible, which probably means a builtin.

On the other hand, it seems to me like 'a.__index__()' *should* be "the right thing" to do, but I get the feeling that making that so would be an astronomically huge change without much real benefit and lots of opportunities to break everything.  I suspect I'm also missing something fundamental in why it's not the right thing to do.
Date User Action Args
2013-08-19 20:43:39zach.waresetrecipients: + zach.ware, arigo, mark.dickinson, eric.snow, serhiy.storchaka
2013-08-19 20:43:39zach.waresetmessageid: <>
2013-08-19 20:43:39zach.warelinkissue18712 messages
2013-08-19 20:43:39zach.warecreate