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, ezio.melotti, michael.foord
Date 2010-11-25.22:08:33
SpamBayes Score 8.19558e-07
Marked as misclassified No
Message-id <1290722916.62.0.0639858562622.issue10535@psf.upfronthosting.co.za>
In-reply-to
Content
Warnings should be on by default in unittest so that developers can see them while running the tests even if they are silenced by default in Python.

The plan is to add a "warnings" argument to TestProgram and the default TextTestRunner:
  * if the argument is passed always use it as a filter (e.g. default, ignore, all, ...) for warnings;
  * if the argument is not passed and sys.warnoptions is not [] (i.e. python has been called with "-W something") don't do anything (i.e. use the warnings specified by -W);
  * if the argument is not passed and sys.warnoptions is [], use 'default' (i.e. show warnings).

In order to prevent floods of warnings when the deprecated assertEquals, assert_, etc. are used (see #9424), a new type of warning could be created (e.g. _UnittestDeprecationWarning) and filtered so that these warnings are printed only once.
History
Date User Action Args
2010-11-25 22:08:36ezio.melottisetrecipients: + ezio.melotti, brett.cannon, michael.foord
2010-11-25 22:08:36ezio.melottisetmessageid: <1290722916.62.0.0639858562622.issue10535@psf.upfronthosting.co.za>
2010-11-25 22:08:33ezio.melottilinkissue10535 messages
2010-11-25 22:08:33ezio.melotticreate