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 serhiy.storchaka
Recipients Claudiu.Popa, berker.peksag, daniel.wagner-hall, ezio.melotti, martin.panter, michael.foord, r.david.murray, serhiy.storchaka
Date 2015-05-19.09:14:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1432026868.6.0.475324314482.issue15836@psf.upfronthosting.co.za>
In-reply-to
Content
Core developers left a couple of notes and the patch itself is outdated. Here is updated patch that addresses all comments. It also extends the checking to assertRaisesRegex(), assertWarns() and assertWarnsRegex().

There is a risk to break existing incorrect tests if the argument is a tuple. They can be passed for now because caught exception or warning is found before incorrect value. For example:

    with self.assertRaises((ValueError, None)):
        int('a')
History
Date User Action Args
2015-05-19 09:14:28serhiy.storchakasetrecipients: + serhiy.storchaka, ezio.melotti, r.david.murray, michael.foord, Claudiu.Popa, berker.peksag, martin.panter, daniel.wagner-hall
2015-05-19 09:14:28serhiy.storchakasetmessageid: <1432026868.6.0.475324314482.issue15836@psf.upfronthosting.co.za>
2015-05-19 09:14:28serhiy.storchakalinkissue15836 messages
2015-05-19 09:14:28serhiy.storchakacreate