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 cool-RR
Recipients BreamoreBoy, cool-RR, josh.r, rhettinger
Date 2014-07-03.22:51:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Mark, again I'm finding myself saying things that are obvious to all of us: You can figure out that "tuple index out of range" means you asked for an item bigger than the size of the tuple, but it might be very helpful for debugging to say the number of item that you asked for and the size of the tuple. For example, maybe it'll say "IndexError: tuple only has 0 elements, can't access element number 1" and you'd be like, "hey, this tuple is empty, it's supposed to have stuff, so the bug is that it's empty", or alternatively it might say "IndexError: tuple only has 10 elements, can't access element number 732426563" and then you'd say "oh, there's a bug in the code that says which number of item I want, this number is very likely wrong for my use case".

Was the above paragraph not quite obvious? Can't we all think of many different examples where you'd want to have that information? Why do I really have to go over these things?
Date User Action Args
2014-07-03 22:51:13cool-RRsetrecipients: + cool-RR, rhettinger, BreamoreBoy, josh.r
2014-07-03 22:51:13cool-RRsetmessageid: <>
2014-07-03 22:51:13cool-RRlinkissue21911 messages
2014-07-03 22:51:13cool-RRcreate