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 ezio.melotti
Recipients brett.cannon, eric.araujo, ezio.melotti, michael.foord
Date 2010-11-26.05:18:26
SpamBayes Score 7.07247e-09
Marked as misclassified No
Message-id <>
Here's a working patch (without docs and tests).
I managed to filter the warnings by message without introducing a new type of warning. As it is, all the warnings related to deprecated unittest methods are printed only once per module, regardless of what methods are used and how many times.
I'm also thinking that it might be better to include the name of the deprecated method in the message and use three filters for fail* methods, assert* methods, and the assert*Regexp* methods that will be deprecated. This will show at worst 3 warnings per module, but the assert*Regexp* and the fail* methods are not so common, so it shouldn't be too nosy.
One "limitation" of the patch is that the per-module special-casing for unittest is not affect by the `warnings` argument, but it can be changed when -W is used and no `warnings` arg is passed.

Regrtest doesn't seem to use unittest, so it should be fixed separately (probably needs another issue).
Date User Action Args
2010-11-26 05:18:28ezio.melottisetrecipients: + ezio.melotti, brett.cannon, eric.araujo, michael.foord
2010-11-26 05:18:28ezio.melottisetmessageid: <>
2010-11-26 05:18:26ezio.melottilinkissue10535 messages
2010-11-26 05:18:26ezio.melotticreate