Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #68233

Re: which async framework?

From Sturla Molden <sturla.molden@gmail.com>
Subject Re: which async framework?
Date 2014-03-11 17:44 +0000
References <531E22DF.7030709@simplistix.co.uk> <1733040935416225908.878896sturla.molden-gmail.com@news.gmane.org> <loom.20140311T170030-477@post.gmane.org>
Newsgroups comp.lang.python
Message-ID <mailman.8055.1394559893.18130.python-list@python.org> (permalink)

Show all headers | View raw


Antoine Pitrou <solipsis@pitrou.net> wrote:

> Yes, why use a library when you can rewrite it all yourself?

This assumes something equivalent to the library will have to be written.
But if it can be replaced with something very minimalistic it is just
bloat. I would also like to respond that the select module and pywin32 are
libraries. So what we are talking about here is not using a library versus
issuing low-level system calls, but using a cross-platform library instead
of having separate modules with system calls for Linux, *BSD/Apple and
Windows.

Another thing is that co-routines and "yield from" statements just makes it
hard to follow the logic of the program. I still have to convince myself
that a library for transforming epoll function calls into co-routines is
actually useful. If it just turns otherwise readable code into something
most Python programmers cannot read it is better left out of the project.

Sturla

Back to comp.lang.python | Previous | NextNext in thread | Find similar | Unroll thread


Thread

Re: which async framework? Sturla Molden <sturla.molden@gmail.com> - 2014-03-11 17:44 +0000
  Re: which async framework? Gregory Ewing <greg.ewing@canterbury.ac.nz> - 2014-03-12 10:56 +1300
    Re: which async framework? Marko Rauhamaa <marko@pacujo.net> - 2014-03-12 00:18 +0200

csiph-web