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

[Andrew Bennetts]

John Arbash Meinel wrote:
> Andrew Bennetts wrote:
[...]
> > 
> > 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").
> 
> Well, it sounds like something we will run into in some sort of an sftp
> test if it doesn't happen here. Since PQM runs with -Werror. Is it just
> that dapper paramiko with python2.4 doesn't cause this warning?

Probably, I think it probably only happens with python2.5.

> > 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?
> 
> That seems reasonable. We could even do in in 'bzr' itself with a custom
> filter added. Or set the #! line to be:
> 
> /bin/env python -Wignore
> 
> Though I'm not sure if /bin/env passes parameters correctly on all
> platforms.

I recently discovered this evil trick:

#!/bin/sh
""""exec /usr/bin/env python -Wignore $0 "$@";" """

I found this at
http://mail.python.org/pipermail/python-dev/2007-July/073897.html

-Andrew.