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 mbussonn
Recipients brett.cannon, martin.panter, mbussonn, terry.reedy
Date 2017-02-27.15:44:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1488210270.75.0.177637293324.issue26389@psf.upfronthosting.co.za>
In-reply-to
Content
> Another point is that it may be better to keep the existing parameter name “value”, rather than (eventually?) replacing it with “exc”. I think both of these things could be accomplished by juggling the “value” and “etype” parameters:

I agreed, and that what I would have done outside of CPython, but that felt like this kind of juggling was frowned upon. 

> The disadvantage of any of these changes is that we may want to maintain support for the old signature while Python 2 remains alive.

Your example does not seem to break the old signature. Or I fail to see how.

If that way would be accepted I'm happy to implement it.
History
Date User Action Args
2017-02-27 15:44:30mbussonnsetrecipients: + mbussonn, brett.cannon, terry.reedy, martin.panter
2017-02-27 15:44:30mbussonnsetmessageid: <1488210270.75.0.177637293324.issue26389@psf.upfronthosting.co.za>
2017-02-27 15:44:30mbussonnlinkissue26389 messages
2017-02-27 15:44:30mbussonncreate