chrysn

This does *not* trigger on PyPy, probably because its GC behaves differently.

… and it doesn't trigger with the simple6 transport either.

There are no real facilities in CoAP-over-UDP for larger block sizes than 1024 bytes. You can turn off block-wise transfer, though. How you go about that depends on whether aiocoap...

Where are you using aiocoap in that setup? Are the sensors running Python, or are you replacing the Leshan LwM2M server with an own aiocoap implementation?

So to summarize, you are building an LwM2M client using aiocoap, and your application generates 6x10 sensor data points per second. In what I understand to be the LwM2M fashion,...

Many resources can be observed in parallel; you might be writing in sequential style, which then "blocks" (really, suspends) the task that's observing. In general with waiting for multiple things...

As you use register_callback, you can do that in a single task. You will still need to either * wait for the first response to gather error messages if something...

fileserver has been moved in with tools. Packaging them independently seems to be quite a hassle (having two PyPI packages from one source), not sure how that's best done.

Partially; you can create your context as a server context and bind it to a particular port, then all your UDP communication will happen from there (provided you're on a...

Windows makes things trickier here, because Windows does not support the required IPV6_RECVPKTINFO socket flag that would set the source port on unbound sockets, and for bound sockets there is...