Yes. I may even have filed a ticket for this once. The problem is writing a unit test to prove it's necessary :)
On Fri, Oct 26, 2012 at 12:40 PM, gelin yan <dynami...@gmail.com> wrote: > Hi All > > I just noticed abstract.py from internet/iocpreactor/ has a possible > typo: > > look at the method* *loseConnection > * > * > if self.connected and not self.disconnecting: > if self._writeDisconnected: > # doWrite won't trigger the connection close anymore > self.stopReading() > self.stopWriting > self.connectionLost(_connDone) > else: > self.stopReading() > self.startWriting() > self.disconnecting = 1 > > in the first part I found > self.stopWriting > > Is it a typo for self.stopWriting()? > > > Regards > > gelin yan > > > > > > _______________________________________________ > Twisted-Python mailing list > Twisted-Python@twistedmatrix.com > http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python > > -- Itamar Turner-Trauring, Future Foundries LLC http://futurefoundries.com/ — Twisted consulting, training and support.
_______________________________________________ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
