Message 278334 - 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	ncoghlan
Recipients	Martin Teichmann, Martin.Teichmann, Tim.Graham, eric.snow, ncoghlan, python-dev, serhiy.storchaka
Date	2016-10-09.03:08:17
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<[email protected]>
In-reply-to

Content
Fixing the proposed format string accordingly, and also including the underlying exception type as I did in the examples: f"Error calling __set_name__ on {type(the_attr).__name__!r} instance {the_attr_name!r} in {class_being_defined.__name__!r}: {type(raised_exc).__name__}: {str(raised_exc)}"

Fixing the proposed format string accordingly, and also including the underlying exception type as I did in the examples:

f"Error calling __set_name__ on {type(the_attr).__name__!r} instance {the_attr_name!r} in {class_being_defined.__name__!r}: {type(raised_exc).__name__}: {str(raised_exc)}"

History
Date	User	Action	Args
2016-10-09 03:08:18	ncoghlan	set	recipients: + ncoghlan, python-dev, eric.snow, serhiy.storchaka, Martin.Teichmann, Tim.Graham, Martin Teichmann
2016-10-09 03:08:18	ncoghlan	set	messageid: <[email protected]>
2016-10-09 03:08:18	ncoghlan	link	issue28214 messages
2016-10-09 03:08:17	ncoghlan	create