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 llllllllll
Recipients brett.cannon, llllllllll
Date 2017-05-25.22:41:20
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1495752080.24.0.264186476964.issue30477@psf.upfronthosting.co.za>
In-reply-to
Content
The old error of tuple.index(x): x not in tuple seemed very confusing to me. It was also harder to quickly understand what the program was doing wrong. This saves people a second pass through the program under the debugger because they can just see what the invalid value was.

The reason I am explicitly calling repr instead of using %R is that I didn't want to call repr twice if I didn't need to. If people think that is fine the format can just be tuple.index(%R): %R not in tuple instead.
History
Date User Action Args
2017-05-25 22:41:20llllllllllsetrecipients: + llllllllll, brett.cannon
2017-05-25 22:41:20llllllllllsetmessageid: <1495752080.24.0.264186476964.issue30477@psf.upfronthosting.co.za>
2017-05-25 22:41:20lllllllllllinkissue30477 messages
2017-05-25 22:41:20llllllllllcreate