On Fri, 14 Jan 2005 23:25:21 -0500, Peter Hansen <[EMAIL PROTECTED]> wrote:
>engsol wrote:
>> I didn't fully think through my application before posting my
>> question. Async com port routines to handle com port interrups
>> only work well if one has access to the low level operating
>> system. In
On Sat, 15 Jan 2005 19:38:19 + (UTC), Chris Liechti <[EMAIL PROTECTED]>
wrote:
>engsol <[EMAIL PROTECTED]> wrote in
>news:[EMAIL PROTECTED]:
>
>> I didn't fully think through my application before posting my
>> question. Async com port routines to handle com port interrups
>> only work well
engsol <[EMAIL PROTECTED]> wrote in
news:[EMAIL PROTECTED]:
> I didn't fully think through my application before posting my
> question. Async com port routines to handle com port interrups
> only work well if one has access to the low level operating
> system. In that case the receive buffer inte
engsol wrote:
I didn't fully think through my application before posting my
question. Async com port routines to handle com port interrups
only work well if one has access to the low level operating
system. In that case the receive buffer interrupt would cause
a jump to an interrupt service routine
Thanks much..:)
On 14 Jan 2005 12:25:43 -0800, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
>A search on google gave me this library, I haven't tested it though:
>http://groups-beta.google.com/group/comp.lang.python.announce/browse_frm/thread/6d3263250ed65816/291074d7bd94be63?q=com+port+python&
A search on google gave me this library, I haven't tested it though:
http://groups-beta.google.com/group/comp.lang.python.announce/browse_frm/thread/6d3263250ed65816/291074d7bd94be63?q=com+port+python&_done=%2Fgroups%3Fhl%3Den%26lr%3D%26safe%3Doff%26q%3Dcom+port+python%26qt_s%3DSearch+Groups%26&_do
