Prev: safely returning objects from a Process to the parent through aQueue()
Next: ANN: superpy 1.2.1
From: John Nagle on 7 Nov 2009 00:27
I'm using pySerial to read from a serial port.
One thread reads from the port, with no timeout.
Another thread handles output and other tasks. This works
fine until I want to shut down the program. I can't reliably
break the program out of the read when it's waiting. On Windows,
closing the serial port will abort the read, but that seems to have no
effect on Linux.

I know, I could put a timeout on the read and handle all those
null returns. Is there a better way?

John Nagle
From: Aahz on 11 Nov 2009 20:03
In article <4af50316$0$1610$742ec2ed(a)news.sonic.net>,
John Nagle <nagle(a)animats.com> wrote:
>
>I'm using pySerial to read from a serial port. One thread reads from
>the port, with no timeout. Another thread handles output and other
>tasks. This works fine until I want to shut down the program. I can't
>reliably break the program out of the read when it's waiting. On
>Windows, closing the serial port will abort the read, but that seems to
>have no effect on Linux.
>
>I know, I could put a timeout on the read and handle all those null
>returns. Is there a better way?

No
--
Aahz (aahz(a)pythoncraft.com) <*> http://www.pythoncraft.com/

[on old computer technologies and programmers] "Fancy tail fins on a
brand new '59 Cadillac didn't mean throwing out a whole generation of
mechanics who started with model As." --Andrew Dalke
 | 
Pages: 1
Prev: safely returning objects from a Process to the parent through aQueue()
Next: ANN: superpy 1.2.1