[Zope-dev] New Client.py bug(?) in 2.2.0 affects ZScheduler

In Zope version 2.2.0b3 Client.py calls connect in httplib (in two different places) like this: sock.connect(self.host,self.port) In Zope version 2.2.0 (final) it's like this: sock.connect((self.host,self.port)) In the latter case, Python complains: TypeError: 'argument 1: ..., tuple found' Does anyone know what was the motivation for the change in the syntax for the call to connect? Should I drop this in the Collector? -- Loren