Discussion of Python 3.5 support
MicroPython aims to implement the Python 3.x "standard". At the moment x is currently 4, ie we try to be compatible with CPython 3.4. It's new territory as to what to do when CPython evolves to larger version numbers. I would say we should try to follow the changes and implement them when possible/sensible.
Python 3.5 had a feature freeze on 24 May 2015 and is scheduled for final release on 13 September 2015. This ticket here is about discussing if, what and how we should upgrade uPy to version 3.5 of the language. It may be that some issues need to break off into separate tickets and that's fine but we should link to them from this one.
The PEP discussing the new features in 3.5: https://www.python.org/dev/peps/pep-0478/
A more friendly overview in the docs: https://docs.python.org/3.5/whatsnew/3.5.html
Below is a list of finalised/accepted PEPs for 3.5 grouped into their impact to MicroPython.
Extensions to the syntax:
- PEP 448 - additional unpacking generalizations; see #5807
- PEP 465 - a new matrix multiplication operator; done in 2069c563f9e944d8f45e524b425fff23208e8153
- PEP 492 - coroutines with async and await syntax
Extensions and changes to the runtime:
- PEP 461 - %-formatting for binary strings - tentatively done
- PEP 475 - retrying system calls that fail with EINTR - done in 9418611c8aa860812e28b6e2b6bfde7be5817b43
- PEP 479 - change StopIteration handling inside generators - done in 3f6ffe059f64b3ebc44dc0bbc63452cb8850702b
Standard library changes:
- PEP 471 - os.scandir()
- PEP 485 - math.isclose(), a function for testing approximate equality - done in af5c998f37ddc62abfd36e0b8be511c392fc25d8
Miscellaneous changes that are not relevant to MicroPython:
- PEP 441 - improved Python zip application support
- PEP 486 - make the Python Launcher aware of virtual environments
- PEP 484 - type hints (advisory only)
- PEP 488 - elimination of PYO files
- PEP 489 - redesigning extension module loading
- Added the
"namereplace"error handlers. The"backslashreplace"error handlers now work with decoding and translating. - Property docstrings are now writable. This is especially useful for collections.namedtuple() docstrings.
- Circular imports involving relative imports are now supported.
Changes to MicroPython built-in modules
- asyncio (many, may need another ticket)
- cmath - A new function
isclose()provides a way to test for approximate equality.
- collections
- The
OrderedDictclass is now implemented in C, which makes it 4 to 100 times faster. -
OrderedDict.items(),OrderedDict.keys(),OrderedDict.values()views now supportreversed()iteration. - The deque class now defines
index(),insert(), andcopy(), and supports the + and * operators. - Docstrings produced by
namedtuple()can now be updated. - The
UserStringclass now implements the__getnewargs__(),__rmod__(),casefold(),format_map(),isprintable(), andmaketrans()methods to match the corresponding methods ofstr.
- The
- heapq - Element comparison in
merge()can now be customized by passing a key function in a new optional key keyword argument, and a new optionalreversekeyword argument can be used to reverse element comparison - io - A new
BufferedIOBase.readinto1()method, that uses at most one call to the underlying raw stream'sRawIOBase.read()orRawIOBase.readinto()methods. - json - JSON decoder now raises
JSONDecodeErrorinstead ofValueErrorto provide better context information about the error.
- math
- Two new constants have been added to the math module:
infandnan. - A new function
isclose()provides a way to test for approximate equality. - A new
gcd()function has been added. Thefractions.gcd()function is now deprecated.
- Two new constants have been added to the math module:
- os
- The new
scandir()function returning an iterator ofDirEntryobjects has been added. - The
urandom()function now uses thegetrandom()syscall on Linux 3.17 or newer, and getentropy() on OpenBSD 5.6 and newer, removing the need to use /dev/urandom and avoiding failures due to potential file descriptor exhaustion. - New
get_blocking()andset_blocking()functions allow getting and setting a file descriptor's blocking mode (O_NONBLOCK.) - There is a new
os.path.commonpath()function returning the longest common sub-path of each passed pathname.
- The new
- re
- References and conditional references to groups with fixed length are now allowed in lookbehind assertions.
- The number of capturing groups in regular expressions is no longer limited to 100.
- The
sub()andsubn()functions now replace unmatched groups with empty strings instead of raising an exception. - The
re.errorexceptions have new attributes,msg,pattern,pos,lineno, andcolno, that provide better context information about the error
- socket
- Functions with timeouts now use a monotonic clock, instead of a system clock.
- A new
socket.sendfile()method allows sending a file over a socket by using the high-performanceos.sendfile()function on UNIX, resulting in uploads being from 2 to 3 times faster than when using plainsocket.send(). - The
socket.sendall()method no longer resets the socket timeout every time bytes are received or sent. The socket timeout is now the maximum total duration to send all data. - The backlog argument of the
socket.listen()method is now optional. By default it is set to SOMAXCONN or to 128, whichever is less.
- ssl
- Memory BIO Support
- Application-Layer Protocol Negotiation Support
- There is a new
SSLSocket.version()method to query the actual protocol version in use. - The
SSLSocketclass now implements aSSLSocket.sendfile()method. - The
SSLSocket.send()method now raises either thessl.SSLWantReadErrororssl.SSLWantWriteErrorexception on a non-blocking socket if the operation would block. Previously, it would return 0. - The
cert_time_to_seconds()function now interprets the input time as UTC and not as local time, per RFC 5280. Additionally, the return value is always an int. - New
SSLObject.shared_ciphers()andSSLSocket.shared_ciphers()methods return the list of ciphers sent by the client during the handshake. - The
SSLSocket.do_handshake(),SSLSocket.read(),SSLSocket.shutdown(), andSSLSocket.write()methods of theSSLSocketclass no longer reset the socket timeout every time bytes are received or sent. - The
match_hostname()function now supports matching of IP addresses.
- sys
- A new
set_coroutine_wrapper()function allows setting a global hook that will be called whenever a coroutine object is created by an async def function. A correspondingget_coroutine_wrapper()can be used to obtain a currently set wrapper. - A new
is_finalizing()function can be used to check if the Python interpreter is shutting down.
- A new
- time The
monotonic()function is now always available.
(Changes to non-built-in modules will need to be documented elsewhere.)
The above list should be edited if/when progress is made on a given feature.
PEP 634 Structural Pattern Matching (Python 3.10) support
CPython 3.10 release candidate 2 is now out, and the final release is less than two weeks away. By far the biggest change in the release is support for the new Structural Pattern Matching syntax. This is by far the most substantial language change Python has seen since the arrival of the walrus operator :=, and probably since the release of Python 3.
(Those not familiar with Structural Pattern Matching should probably start by reading PEP 635 which covers the motivation for this new language feature. There are separate PEPs for the full specification and a tutorial.)
Structural Pattern Matching is a big and fairly complex feature; adding it to Micropython would be a fair amount of work and add quite a bit of code to the parser. How much work and how much code are open questions, as is the question of when, if ever, it will be worth doing? The answer to this last question will depend very much on how rapidly users of CPython embrace, and come to depend on, this new feature. That said, the new syntax can save a lot of source code typing; if it gets rapid and windspread uptake it would represent a substantial incompatibility between Micropython and CPython.
Given how significant an addition this is to the Python syntax, it seems like it would be a good idea to understand the work involved and the scope of the change well before use of it in CPython becomes widespread. I am opening this issue to serve as a place to discuss those topics.