Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!nntp.club.cc.cmu.edu!micro-heart-of-gold.mit.edu!bloom-beacon.mit.edu!bloom-beacon.mit.edu!panix!not-for-mail From: Grant Edwards Newsgroups: comp.lang.python Subject: Re: which async framework? Date: Tue, 11 Mar 2014 16:52:18 +0000 (UTC) Organization: PANIX Public Access Internet and UNIX, NYC Lines: 32 Message-ID: References: <531E22DF.7030709@simplistix.co.uk> <1733040935416225908.878896sturla.molden-gmail.com@news.gmane.org> NNTP-Posting-Host: dsl.comtrol.com X-Trace: reader1.panix.com 1394556738 26636 64.122.56.22 (11 Mar 2014 16:52:18 GMT) X-Complaints-To: abuse@panix.com NNTP-Posting-Date: Tue, 11 Mar 2014 16:52:18 +0000 (UTC) User-Agent: slrn/1.0.1 (Linux) Xref: csiph.com comp.lang.python:68227 On 2014-03-11, Antoine Pitrou wrote: > Sturla Molden gmail.com> writes: >> >> Chris Withers simplistix.co.uk> wrote: >> > Hi All, >> > >> > I see python now has a plethora of async frameworks and I need to try >> > and pick one to use from: >> > >> > - asyncio/tulip >> > - tornado >> > - twisted >> >> I'd go for using iocp, epoll and kqueue/kevent directly. Why bother to >> learn a framework? You will find epoll and kqueue/kevent in the select >> module and iocp in pywin32. > > Yes, why use a library when you can rewrite it all yourself? > Actually, you should probably issue system calls to the kernel directly, > the libc is overrated (as is portability, I suppose). And don't bother with device drivers for the network adapters either. Just map their PCI regions in to user-space and twiddle the reigisters directly! ;) [I do that when testing PCI boards with C code, and one of these days I'm going to figure out how to do it with Python.] -- Grant Edwards grant.b.edwards Yow! It's a hole all the at way to downtown Burbank! gmail.com