It does appear that upstream introduced the error in paramiko/sftp_client.py:109 while trying to resolve the logger leaks issue. The issue is in the _log calling self.sock.get_name which I believe is attempting to get the channel name. I don't see any fixes in upstreams source repository but will continue to try and find a fix.
On Wed, May 7, 2008 at 4:18 PM, Jeremy Bouse <[EMAIL PROTECTED]> wrote: > I'll have to investigate further to see if upstream has issued any bug fix > patches for this or determine if there was an incompatible API changes made. > > > On Mon, May 5, 2008 at 12:52 PM, Simon McVittie <[EMAIL PROTECTED]> wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Package: python-paramiko >> Version: 1.7.3-1 >> Severity: normal >> Tags: upstream >> >> When Paramiko is updated to version 1.7.3-1, bzr commit to a remote >> location >> fails; downgrading to 1.7.2-0.1 works again. The traceback closely >> resembles >> that of upstream bug <https://bugs.launchpad.net/paramiko/+bug/209849>. >> >> - -- System Information: >> Debian Release: lenny/sid >> APT prefers unstable >> APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (101, >> 'experimental') >> Architecture: i386 (i686) >> >> Kernel: Linux 2.6.25-1-686 (SMP w/2 CPU cores) >> Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) >> Shell: /bin/sh linked to /bin/bash >> >> Versions of packages python-paramiko depends on: >> ii python 2.5.2-1 An interactive high-level >> object-o >> ii python-crypto 2.0.1+dfsg1-2.1 cryptographic algorithms and >> proto >> ii python-support 0.7.7 automated rebuilding support >> for P >> >> python-paramiko recommends no packages. >> >> - -- no debconf information >> -----BEGIN PGP SIGNATURE----- >> >> iD8DBQFIHztBWSc8zVUw7HYRAsi3AJ96206DbJQGll/Z/+klEcts0CWODwCg62Qw >> pSpz31rXY9fgo6S4yMxz4Gg= >> =6b67 >> -----END PGP SIGNATURE----- >> >> >> >
