From 2746d449067e3e25afe8d2afaf1e5bf740d9c20c Mon Sep 17 00:00:00 2001
From: Robey Pointer <robey@lag.net>
Date: Mon, 28 Feb 2005 07:17:21 +0000
Subject: [PATCH] [project @
 Arch-1:robey@lag.net--2003-public%secsh--dev--1.0--patch-152] little doc
 fixes stupid little doc fixups that didn't fit with the other patches.

---
 paramiko/auth_transport.py | 2 +-
 tests/loop.py              | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/paramiko/auth_transport.py b/paramiko/auth_transport.py
index b6da9bb..32e99ba 100644
--- a/paramiko/auth_transport.py
+++ b/paramiko/auth_transport.py
@@ -53,7 +53,7 @@ class Transport (BaseTransport):
         self.auth_fail_count = 0
 
     def __repr__(self):
-        out = '<paramiko.Transport at %s' % hex(id(self))
+        out = '<paramiko.Transport at %s' % hex(long(id(self)) & 0xffffffffL)
         if not self.active:
             out += ' (unconnected)'
         else:
diff --git a/tests/loop.py b/tests/loop.py
index 9a9734a..22a173f 100644
--- a/tests/loop.py
+++ b/tests/loop.py
@@ -28,7 +28,7 @@ import threading, socket
 class LoopSocket (object):
     """
     A LoopSocket looks like a normal socket, but all data written to it is
-    delivered on the read-end of another LoopSocket, and vice versa,  It's
+    delivered on the read-end of another LoopSocket, and vice versa.  It's
     like a software "socketpair".
     """