The silencing of DeprecationWarning was not taking -3 into consideration. Since
commite038a71053b2456c70c11fd3be471fcd9f048ad9
authorbrett.cannon <brett.cannon@6015fed2-1504-0410-9fe1-9d1591cc4771>
Thu, 14 Jan 2010 20:00:28 +0000 (14 20:00 +0000)
committerbrett.cannon <brett.cannon@6015fed2-1504-0410-9fe1-9d1591cc4771>
Thu, 14 Jan 2010 20:00:28 +0000 (14 20:00 +0000)
treea38c63dceb3540361c461058c63909ef03d662f9
parent06537430506637459e87f5d0e01b58b3b43027cd
The silencing of DeprecationWarning was not taking -3 into consideration. Since
Py3K warnings are DeprecationWarning by default this was causing -3 to
essentially be a no-op. Now DeprecationWarning is only silenced if -3 is not
used.

Closes issue #7700. Thanks Ezio Melotti and Florent Xicluna for patch help.

git-svn-id: http://svn.python.org/projects/python/trunk@77505 6015fed2-1504-0410-9fe1-9d1591cc4771
Lib/warnings.py
Misc/NEWS
Python/_warnings.c