Rev 3435: Add comments in NEWS and HACKING about Deprecation Warnings in http://bzr.arbash-meinel.com/branches/bzr/1.6-dev/dep_warnings

John Arbash Meinel john at arbash-meinel.com
Thu May 29 15:04:40 BST 2008


At http://bzr.arbash-meinel.com/branches/bzr/1.6-dev/dep_warnings

------------------------------------------------------------
revno: 3435
revision-id: john at arbash-meinel.com-20080529140425-z0ycjav1ia7nl454
parent: john at arbash-meinel.com-20080528232033-cx3l3yg845udklps
committer: John Arbash Meinel <john at arbash-meinel.com>
branch nick: dep_warnings
timestamp: Thu 2008-05-29 09:04:25 -0500
message:
  Add comments in NEWS and HACKING about Deprecation Warnings
modified:
  NEWS                           NEWS-20050323055033-4e00b5db738777ff
  doc/developers/HACKING.txt     HACKING-20050805200004-2a5dc975d870f78c
-------------- next part --------------
=== modified file 'NEWS'
--- a/NEWS	2008-05-27 01:05:57 +0000
+++ b/NEWS	2008-05-29 14:04:25 +0000
@@ -14,6 +14,10 @@
 
   CHANGES:
 
+    * Deprecation warnings will not be suppressed when running ``bzr selftest``
+      so that developers can see if their code is using deprecated functions.
+      (John Arbash Meinel)
+
   FEATURES:
 
     * Adding ``-Derror`` will now display a traceback when a plugin fails to

=== modified file 'doc/developers/HACKING.txt'
--- a/doc/developers/HACKING.txt	2008-05-09 06:46:17 +0000
+++ b/doc/developers/HACKING.txt	2008-05-29 14:04:25 +0000
@@ -701,6 +701,13 @@
 the expected deprecation message, and also returns the real result from
 the method, so that tests can keep running.
 
+Deprecation warnings will be suppressed for final releases, but not for
+development versions or release candidates, or when running ``bzr
+selftest``. This gives developers information about whether their code is
+using deprecated functions, but avoids confusing users about things they
+can't fix.
+
+
 Coding Style Guidelines
 =======================
 



More information about the bazaar-commits mailing list