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 pitrou
Recipients adaptivelogic, eric.snow, gvanrossum, martius, ncoghlan, pitrou, rbcollins, rhettinger, vstinner, yselivanov
Date 2015-01-26.23:34:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In-reply-to <>
Le 27/01/2015 00:30, Robert Collins a écrit :
> Robert Collins added the comment:
> So its fairly simple IMO: it will be more code, not less, to support
the non-triple API, *and* it can be added later, unless we're proposing
not to support the triple API at all (which hasn't been proposed AFAICT).

I am proposing it. Passing a single exception instance is the natural
way of expressing such an API. Crippling Python 3 APIs for the purpose
of backwards compatibility is not ok.

Nobody wants to write some_func(exc.__class__, exc, exc.__traceback__)
when they could simply write some_func(exc).
Date User Action Args
2015-01-26 23:34:01pitrousetrecipients: + pitrou, gvanrossum, rhettinger, ncoghlan, vstinner, rbcollins, eric.snow, yselivanov, adaptivelogic, martius
2015-01-26 23:34:01pitroulinkissue17911 messages
2015-01-26 23:34:01pitroucreate