New Client.py bug(?) in 2.2.0 affects ZScheduler
28 Jul
2000
28 Jul
'00
10:34 p.m.
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
28 Jul
28 Jul
10:54 p.m.
New subject: [Zope-dev] New Client.py bug(?) in 2.2.0 affects ZScheduler
Loren Stafford wrote:
Does anyone know what was the motivation for the change in the syntax for the call to connect?
To make it Python 2 compatible, but this shouldn't cause these errors since connect is supposed to be able to takea tuple now. Confusedly, Chris
9406
Age (days ago)
9406
Last active (days ago)
1 comments
2 participants
participants (2)
-
Chris Withers -
Loren Stafford