[RFC] Deprecation warnings considered harmful

Martin Pool mbp at sourcefrog.net
Fri Jun 22 06:06:36 BST 2007


On 6/22/07, Robert Collins <robertc at robertcollins.net> wrote:
> During a discussion with Aaron about the version compatability api I
> proposed, he noted that one of the reasons for bzrtools strict
> compatibility requirement is to avoid users complaining about
> deprecation warnings when in fact its just that bzrtools needs an
> upgrade.
>
> We could address this (as deprecations are meant to be compatible) by
> disabling deprecations in the normal use of bzr from the command line.
> External library users, and our test suite, will still benefit from them
> - we'd want run_bzr to keep them enabled so that we catch them in tests.

That makes sense.  It should be just a one-line change to call into
the warnings library and turn them off.

It would be nice if -Werror still had the usual effect though.  I do
use that from time to time if trying to eliminate a warning.

-- 
Martin



More information about the bazaar mailing list