On Fri, Aug 11, 2017 at 6:46 AM, Barry Scott
wrote:
> I porting some code to latest twisted and I;m seeing the old code expects
> to
> call loseConenction with a reason.
>
This code makes the mistake of treating a peculiarity of a particular
implementation of an interface as the interface itself
I porting some code to latest twisted and I;m seeing the old code expects to
call loseConenction with a reason.
But loseConnection in class ConnectionMixin does not have the parameter.
Is this an oversight or deliberate?
Barry
___
Twisted-Python mail
