Hopefully it doesn't use select if no timeout is set... --Guido van Rossum (sent from Android phone) On Mar 14, 2012 2:08 AM, "Antoine Pitrou" <solip...@pitrou.net> wrote:
> On Wed, 14 Mar 2012 04:26:16 +0000 > Kristján Valur Jónsson <krist...@ccpgames.com> wrote: > > Hi there. > > I want to mention some issues I've had with the socketserver module, and > discuss if there's a way to make it nicer. > > So, for a long time we were able to create magic stackless mixin classes > for > > it, like ThreadingMixIn, and assuming we had the appropriate socket > > replacement library, be able to use it nicely using tasklets. > > I don't really think the ability to "create magic stackless mixin > classes" should be a driving principle for the stdlib. > I would suggest using a proper non-blocking framework such as Twisted. > > > So, my first question is: Why not simply rely on the already built-in > timeout > > support in the socket module? > > In case you didn't notice, the built-in timeout support *also* uses > select(). > > Regards > > Antoine. > > > _______________________________________________ > Python-Dev mailing list > Python-Dev@python.org > http://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > http://mail.python.org/mailman/options/python-dev/guido%40python.org >
_______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
