micropython-lib/micropython
Jim Mussared dc03b4af4d aioble: Fix notified/indicated event waiting.
After a client does a successful `await char.notified()`, then before the
next call to `notified()` a notification arrives, then they call
`notified()` twice before the _next_ notification, the second call will
return None rather than waiting.

This applies the same fix as in 5a86aa5866
which solved a similar problem for server-side `char.written()`. Using
a deque is slightly overkill here, but it's consistent with the server
side, and also makes it very easy to support having a notification queue
in the future.

Also makes the client characteristic properly flags/properties-aware (i.e.
explicitly fail operations that aren't supported).

Signed-off-by: Jim Mussared <jim.mussared@gmail.com>
2021-11-08 17:34:08 +11:00
..
bluetooth/aioble aioble: Fix notified/indicated event waiting. 2021-11-08 17:34:08 +11:00
test.support all: Run black over all code. 2021-05-27 15:50:04 +10:00
uaiohttpclient all: Run black over all code. 2021-05-27 15:50:04 +10:00
ucontextlib all: Run black over all code. 2021-05-27 15:50:04 +10:00
udnspkt all: Run black over all code. 2021-05-27 15:50:04 +10:00
umqtt.robust all: Run black over all code. 2021-05-27 15:50:04 +10:00
umqtt.simple all: Run black over all code. 2021-05-27 15:50:04 +10:00
upip all: Run black over all code. 2021-05-27 15:50:04 +10:00
upysh all: Run black over all code. 2021-05-27 15:50:04 +10:00
urllib.urequest all: Run black over all code. 2021-05-27 15:50:04 +10:00
utarfile all: Run black over all code. 2021-05-27 15:50:04 +10:00
xmltok all: Run black over all code. 2021-05-27 15:50:04 +10:00
README.md all: Update READMEs. 2021-05-27 15:41:08 +10:00

README.md

MicroPython-specific libraries

These are libraries that have been written specifically for use on MicroPython.

In some cases, the libraries are inspired by or based on equivalent CPython standard libraries, but compatibility varies. The libraries are often named with a "u" prefix.

Other libraries have been written specifically for MicroPython use cases.

Future plans

  • More organised directory structure based on library purpose (e.g. drivers, network, etc).