ANN: pySerial 3.0
A new release of pySerial is available. There have been a lot of changes so that the major version was bumped up to 3.0. Changes include (since V2.7): - Python 2.7 and Python 3.2+ from the same sources (lib2to3 is no longer used) - new API, more properties, the set functions are deprecated. (old API still supported for backward compatibility) - Updated miniterm (uses Unicode for console output, supports encodings on serial port, nicer port selection and more). - IPv6 support for rfc2217:// and socket:// - New spy:// handler to log traffic and control calls. - New alt:// handler to select implementations - URL parameters have changed - Experimental classes for easy threading support - Experimental asyncio support (posix) - A number of bugfixes. See https://github.com/pyserial/pyserial/blob/master/CHANGES.rst for more details. Changes in development: - SVN -> GIT - moved (from SF) to github: https://github.com/pyserial/pyserial Currently unsupported is the Jython platform (lack of testing). Download at: https://github.com/pyserial/pyserial/releases or via PyPI: https://pypi.python.org/pypi/pyserial Docs: http://pythonhosted.org/pyserial/ (stable) https://pyserial.readthedocs.org/en/latest/ (follows git) chris -- https://mail.python.org/mailman/listinfo/python-announce-list Support the Python Software Foundation: http://www.python.org/psf/donations/
ANN: pySerial 3.0a0
A new prerelease of pySerial is available. There have been a lot of changes so that the major version was bumped up to 3. Changes include: - Python 2.7 and Python 3.2+ from the same sources (lib2to3 is no longer used) - More properties, the set functions are deprecated. - Updated miniterm (uses Unicode for console output, supports encodings on serial port, nicer port selection and more). - IPv6 support for rfc2217:// and socket:// - New spy:// handler to log traffic and control calls. - URL parameters have changed. - Experimental asyncio support (posix) - A number of other bugfixes. - And more... See https://github.com/pyserial/pyserial/blob/master/CHANGES.rst for more details. Changes in development: - SVN -> GIT - moved (from SF) to github: https://github.com/pyserial/pyserial Currently unsupported is the Jython platform (lack of testing). Download at: https://github.com/pyserial/pyserial/releases Docs: https://pyserial.readthedocs.org/en/latest/ chris -- https://mail.python.org/mailman/listinfo/python-announce-list Support the Python Software Foundation: http://www.python.org/psf/donations/
pySerial 2.5-rc2 (2nd release candidate)
I'm happy to announce a release candidate of pySerial: 2.5-rc2 http://pyserial.sourceforge.net/ Whats new since rc1: - Several small bugfixes. - updated RFC2217 implementation, client support. - changed Posix read implementation (error handling for disconnected devices) - See CHANGES.txt in the distribution for full list. Source archive and Windows installers can be downloaded from here: http://sourceforge.net/projects/pyserial/files/ The Windows installer for Python 3.x has py3k in its name, the other one is for Python 2.x. The source archive's setup.py should automatically convert using 2to3 when run with Python 3.x. chris -- What is pySerial? Quoting from the home page: This module encapsulates the access for the serial port. It provides backends for Python running on Windows, Linux, BSD (possibly any POSIX compliant system), Jython and IronPython (.NET and Mono). The module named serial automatically selects the appropriate backend. -- http://mail.python.org/mailman/listinfo/python-announce-list Support the Python Software Foundation: http://www.python.org/psf/donations/
[issue6586] Documentation of os.write and os.read are inaccurate.
New submission from Chris Liechti cliec...@users.sourceforge.net: Documentation of os.write and os.read are inaccurate, it states that the methods work with 'str' (or strings), which is wrong. - os.write expects an instance of bytes or buffer - os.read returns an instance of bytes The implementation is OK, it fits well with the new io library but the docs don't describe the implementation. -- assignee: georg.brandl components: Documentation messages: 90983 nosy: cliechti, georg.brandl severity: normal status: open title: Documentation of os.write and os.read are inaccurate. versions: Python 3.0, Python 3.1, Python 3.2 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6586 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
Re: Com port interrupts again
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 interrupt would cause a jump to an interrupt service routine.. I don't believe that i would not go that route... the operating system provides sync and async methods to access the serial port. it would make sense to use these before hacking the operating system. (also see below) Python provides that capabilty directly. The solution then would be to write a C extention? ctypes can do many things without a C compiler. it's a very nice an valuable extension, but i won't like to encurage to use it for this particular problem. The suggestions offered by respondents to my original post were almost all of a Use threads, and poll as needed flavor. You're right...I need to learn threads as applied to com ports. if you realy want to do async programming, have a look at twisted (http://twistedmatrix.com). it does not only provide async access to the serial port (trough pyserial + some code in twisted) it also delivers some nice utility functions, classes etc, like the reactor, defereds, thread pools (if you can't resist ;-) and many protocol handlers. chris -- Chris [EMAIL PROTECTED] -- http://mail.python.org/mailman/listinfo/python-list
