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 gvanrossum, ncoghlan, yselivanov
Date 2015-05-21.07:13:28
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1432192408.93.0.377419249254.issue24237@psf.upfronthosting.co.za>
In-reply-to
Content
Why the switch to WriteUnraisable? Unlike __del__ methods and similar operations that may be invoked at arbitrary points, there's nothing stopping us from emitting an exception here - indeed, we're *already* handling an exception.

Getting a hard failure on deprecations is one of the expected consequences of using "-Wall" rather than the default settings.
History
Date User Action Args
2015-05-21 07:13:28ncoghlansetrecipients: + ncoghlan, gvanrossum, yselivanov
2015-05-21 07:13:28ncoghlansetmessageid: <1432192408.93.0.377419249254.issue24237@psf.upfronthosting.co.za>
2015-05-21 07:13:28ncoghlanlinkissue24237 messages
2015-05-21 07:13:28ncoghlancreate