Skip to content

Commit bc278d2

Browse files
committed
Fixs to FASTPOLL.md.
1 parent c57486b commit bc278d2

File tree

1 file changed

+15
-13
lines changed

1 file changed

+15
-13
lines changed

FASTPOLL.md

Lines changed: 15 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -16,23 +16,25 @@ This version has the following changes:
1616
[PR287](https://github.com/micropython/micropython-lib/pull/287).
1717
* Tasks can yield with low priority, running when nothing else is pending.
1818
* Callbacks can similarly be scheduled with low priority.
19-
* The bug with read/write device drivers is fixed (forthcoming PR).
19+
* The bug with read/write device drivers is fixed.
2020
* An assertion failure is produced if `create_task` or `run_until_complete`
2121
is called with a generator function
2222
[PR292](https://github.com/micropython/micropython-lib/pull/292). This traps
2323
a common coding error which otherwise results in silent failure.
24-
25-
A key advantage of this version is that priority device drivers are written
26-
entirely by using the officially-supported technique for writing stream I/O
27-
drivers. If official `uasyncio` acquires a means of prioritising I/O by other
28-
means than by these proposals, application code changes are likely to be
29-
minimal. Using the priority mechanism in this version requires a change to just
30-
one line of code compared to an application running under the official version.
31-
32-
The high priority mechanism formerly provided in `asyncio_priority.py` is
33-
replaced with a faster and more efficient way of handling asynchronous events
34-
with minimum latency. Consequently `asyncio_priority.py` is obsolete and should
35-
be deleted from your system.
24+
* The version and the presence of an event loop instance can be tested at
25+
runtime.
26+
27+
Note that priority device drivers are written by using the officially supported
28+
technique for writing stream I/O drivers. If official `uasyncio` acquires a
29+
means of prioritising I/O other than that in this version, application code
30+
changes should be minimal. Using the fast I/O mechanism in this version
31+
requires changing just one line of code compared to running under the official
32+
version.
33+
34+
The high priority mechanism formerly provided in `asyncio_priority.py` was a
35+
workround based on the view that stream I/O written in Python would remain
36+
unsupported. This is now available so `asyncio_priority.py` is obsolete and
37+
should be deleted from your system.
3638

3739
The facility for low priority coros formerly provided by `asyncio_priority.py`
3840
is now implemented.

0 commit comments

Comments
 (0)