Message 288617 - Python tracker

➜

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	docs@python, mbussonn
Date	2017-02-27.01:21:37
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1488158499.0.0.645448196253.issue29660@psf.upfronthosting.co.za>
In-reply-to

Content
As far as I can tell, http://bugs.python.org/issue17911 made a couple of function in traceback ignore their first arguments (etype) and infer the type from the second one (evalue). (In git 6bc2c1e7 and 2f0441f0 respectively). At least print_exception and format_exception are affected. This likely affect http://bugs.python.org/issue26389 (who wish to expand same API to remove these parameters). And inconsistency with `format_exception_only` which does need `etype` should be checked. If etype is a deprecated parameter it should be noted, and should likely raise a DeprecationWarning as well when set.

As far as I can tell, http://bugs.python.org/issue17911 made a couple of function in traceback ignore their first arguments (etype) and infer the type from the second one (evalue). 

(In git 6bc2c1e7 and 2f0441f0 respectively).

At least print_exception and format_exception are affected.

This likely affect http://bugs.python.org/issue26389 (who wish to expand same API to remove these parameters).

And inconsistency with `format_exception_only` which does need `etype` should be checked. 

If etype is a deprecated parameter it should be noted, and should likely raise a DeprecationWarning as well when set.

History
Date	User	Action	Args
2017-02-27 01:21:39	mbussonn	set	recipients: + mbussonn, docs@python
2017-02-27 01:21:39	mbussonn	set	messageid: <1488158499.0.0.645448196253.issue29660@psf.upfronthosting.co.za>
2017-02-27 01:21:38	mbussonn	link	issue29660 messages
2017-02-27 01:21:37	mbussonn	create