Bug 90161 – master.cfg unittest cleanup: Show DeprecationWarnings with python >= 2.7 too

• Status: RESOLVED
• Resolution: FIXED
• Component: Tools / Tests

[Csaba Osztrogonác]

http://docs.python.org/dev/whatsnew/2.7.html

"A policy decision was made to silence warnings only of interest to developers. DeprecationWarning and its descendants are now ignored unless otherwise requested, preventing users from seeing warnings triggered by an application. This change was also made in the branch that will become Python 3.2. (Discussed on stdlib-sig and carried out in issue 7319.)

In previous releases, DeprecationWarning messages were enabled by default, providing Python developers with a clear indication of where their code may break in a future major version of Python.

However, there are increasingly many users of Python-based applications who are not directly involved in the development of those applications. DeprecationWarning messages are irrelevant to such users, making them worry about an application that’s actually working correctly and burdening application developers with responding to these concerns.

You can re-enable display of DeprecationWarning messages by running Python with the -Wdefault (short form: -Wd) switch, or by setting the PYTHONWARNINGS environment variable to "default" (or "d") before running Python. Python code can also re-enable them by calling warnings.simplefilter('default')."


If you run mastercfg_unittest.py with python 2.7 or newer, you can't see DepricationWarnings come from buildbot.

[Csaba Osztrogonác]

Created attachment 149925 [details]
Patch

[Peter Gal]

(In reply to comment #1)
> Created an attachment (id=149925) [details]
> Patch

lgtm.

[Eric Seidel (no email)]

Comment on attachment 149925 [details]
Patch

OK.

[WebKit Review Bot]

Comment on attachment 149925 [details]
Patch

Clearing flags on attachment: 149925

Committed r125372: <http://trac.webkit.org/changeset/125372>

[WebKit Review Bot]

All reviewed patches have been landed.  Closing bug.