Ed Suominen wrote:
> I'd like to start a discussion on whether Twisted ought to be a part of
> Python's standard library. I understand some of the developers think it
> should not, but I personally don't like seeing far inferior networking
> code sitting there in stdlib. Inclusion in the stdlib carries an
> implied endorsement, and that endorsement should be going to Twisted,
> in my view.
Exarkun pointed out some really good reasons why Twisted should not be
in stdlib. I pretty much agree with him.
However, there is something that could be done to stdlib:
refactor the various networking things there so, that they are built
out of modules that only implement protocol logic, and blocking
"runners" for the protocol logic.
That is, separate the socket calls from the protocol. The interface
between them would probably look a lot like a twisted Protocol, and
hopefully would enable code reuse (in either direction).