Rev 4682: Fix bug #44062, Always suppress deprecation warnings. in

John Arbash Meinel john at
Tue Oct 13 18:06:25 BST 2009


revno: 4682
revision-id: john at
parent: pqm at
committer: John Arbash Meinel <john at>
branch nick: 2.0.2-deprecation-warnings-440062
timestamp: Tue 2009-10-13 12:06:15 -0500
  Fix bug #44062, Always suppress deprecation warnings.
  Python 2.6 now 'comes with' a deprecation warning suppression as part of
  the threading module. So the current check that says 'if someone manually
  configured a deprecation warning filter, don't add ours' now breaks
  because there is always one present.
  So instead, we just always suppress all deprecation warnings if we are in
  a 'final' release.
-------------- next part --------------
=== modified file 'bzrlib/'
--- a/bzrlib/	2009-09-09 14:21:37 +0000
+++ b/bzrlib/	2009-10-13 17:06:15 +0000
@@ -1097,7 +1097,7 @@
     # Is this a final release version? If so, we should suppress warnings
     if bzrlib.version_info[3] == 'final':
-        suppress_deprecation_warnings(override=False)
+        suppress_deprecation_warnings(override=True)
     if argv is None:
         argv = osutils.get_unicode_argv()

More information about the bazaar-commits mailing list