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


Groups > comp.lang.python > #68863

Re: Asyncio (or something better) for control of a vacuum system/components.

From Marko Rauhamaa <marko@pacujo.net>
Newsgroups comp.lang.python
Subject Re: Asyncio (or something better) for control of a vacuum system/components.
Date 2014-03-24 12:22 +0200
Organization A noiseless patient Spider
Message-ID <8738i728xe.fsf@elektro.pacujo.net> (permalink)
References <mailman.8442.1395655124.18130.python-list@python.org>

Show all headers | View raw


Shishir <shishirk@gmail.com>:

> The problem is that self.execute() blocks and the asyncio framework
> has no way to know how to reschedule it or bypass it. This can be
> avoided if I depended on I/O from a file descriptor, on which I can
> apply poll()/select(). But the channel handler that I have is more
> generic (rs232() in code above).

Deep down asyncio depends on file descriptors. If your thingy is another
kind of object, it needs to go into its own process or thread.

> A server sits on the computer which is connected to the devices via
> channels (rs232, rs485, usb etc.). [...]

Sounds about right.

> I have looked around the web but couldn't find an easy+flexible
> framework to do what I have outlined here.

Asyncio + subprocess should be all you need for a framework. However, some
system programming *will* be required.


Marko

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


Thread

Asyncio (or something better) for control of a vacuum system/components. Shishir <shishirk@gmail.com> - 2014-03-24 14:45 +0530
  Re: Asyncio (or something better) for control of a vacuum system/components. Marko Rauhamaa <marko@pacujo.net> - 2014-03-24 12:22 +0200
  Re: Asyncio (or something better) for control of a vacuum system/components. mauro <mauro@gmail.com> - 2014-03-24 12:23 +0000

csiph-web