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 barry, brett.cannon, cvrebert, eric.araujo, ezio.melotti, rhettinger
Date 2013-06-16.03:01:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1371351689.43.0.44981369997.issue18162@psf.upfronthosting.co.za>
In-reply-to
Content
I would also like to see a PEP or good python-dev discussion before embarking on all these API expansions.  There should be an evaluation of whether any existing code would benefit from it, whether the current "args" attribute is sufficient, whether the code bloat is worth it, etc.

Also, I'm unclear on whether you expect users to have to provide the index value in their own code (i.e. is "raise IndexError" to still be permitted or will all pure python code be required to use "raise IndexError(i)" and change existing code if they already use "raise IndexError("Out of range")).

If you don't change requirements for pure python code, then how can be even rely on the new attribute being there (i.e.  is "except IndexError as e:  print(e.index)" guaranteed to work?).
History
Date User Action Args
2013-06-16 03:01:29rhettingersetrecipients: + rhettinger, barry, brett.cannon, ezio.melotti, eric.araujo, cvrebert
2013-06-16 03:01:29rhettingersetmessageid: <1371351689.43.0.44981369997.issue18162@psf.upfronthosting.co.za>
2013-06-16 03:01:29rhettingerlinkissue18162 messages
2013-06-16 03:01:28rhettingercreate