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

Groups > comp.lang.python > #46411 > unrolled thread

Re: The state of pySerial

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: The state of pySerial William Ray Wing <wrw@mac.com> - 2013-05-29 16:00 -0400

#46411 — Re: The state of pySerial

On May 29, 2013, at 2:23 PM, Ma Xiaojun <damage3025@gmail.com> wrote:

> Hi, all.
> 
> pySerial is probably "the solution" for serial port programming.
> Physical serial port is dead on PC but USB-to-Serial give it a second
> life. Serial port stuff won't interest end users at all. But it is
> still used in the EE world and so on. Arduino uses it to upload
> programs. Sensors may use serial port to communicate with PC. GSM
> Modem also uses serial port to communicate with PC.
> 
> Unforunately, pySerial project doesn't seem to have a good state. I
> find pySerial + Python 3.3 broken on my machine (Python 2.7 is OK) .
> There are unanswered outstanding bugs, PyPI page has 2.6 while SF
> homepage still gives 2.5.
> 
> Any idea?
> -- 
> http://mail.python.org/mailman/listinfo/python-list

Let me add another vote/request for pySerial support.  I've been using it with python 2.7 on OS-X, unaware that there wasn't a path forward to python 3.x.  If an external sensor absolutely positively has to be readable, then RS-232 is the only way to go.  USB interfaces can and do lock up if recovery from a power failure puts power on the external side before the computer has finished initializing the CPU side.  RS-232, bless its primitive heart, could care less.

Thanks,
Bill

[toc] | [standalone]

Back to top | Article view | comp.lang.python

csiph-web