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

2000-07-28 Thread Adam Karpierz
>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: > >

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

2000-07-28 Thread Chris Withers
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

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

2000-07-28 Thread Loren Stafford
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: TypeErro