bzrlib.tests.blackbox.test_init.TestSFTPInit fails when run alone

[Andrew Bennetts]

When running just the blackbox tests I see the following failure:

----
$ ./bzr --no-plugins selftest bzrlib.tests.blackbox.test_init.TestSFTPInit
[...]

FAIL: blackbox.test_init.TestSFTPInit.test_init
    not equal:
a = ''
b = "/var/lib/python-support/python2.5/paramiko/message.py:226: DeprecationWarning: integer argument expected, got float\n  self.packet.write(struct.pack('>I', n))\n"
----

This doesn't happen in the full run, because the deprecation warning is only
shown once and gets triggered earlier when it is harmless.

Using a newer version of paramiko solves this particular problem, but the
general issue is that deprecation warnings should not affect the result of
blackbox tests.  If people agree, I'll file a bug about this (probably with
importance "low").

Also, it occurs to me that arguably deprecation warnings should not be shown to
users at all.  Users can't really do anything sensible about API warnings except
guess that upgrading their libraries *might* fix the problem.  It's developers
(and packagers) that ought to be informed, not end users.  Perhaps distributions
like Ubuntu should be suppressing DeprecationWarnings by default in released
versions, and only display them by default for development versions?

-Andrew.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20070718/a765941e/attachment.pgp