| Age | Commit message (Collapse) | Author |
|
|
|
|
|
The argument is optional and if given should be a string naming the
status variable to query.
|
|
Doesn't list specific API calls yet, the purpose is to let user know that
the module exists.
|
|
Plus, additional descriptions/formatting.
|
|
|
|
|
|
|
|
|
|
|
|
And describe an alternative of using uselect.poll().
|
|
|
|
|
|
|
|
I have not actually tested this, going by information available in https://forum.micropython.org/viewtopic.php?t=2584
|
|
|
|
Use the "usocket" module name everywhere. Use "MicroPython port"
terminology. Suggest to avoid using IPPROTO_* constants in socket()
call.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Also renames "stmhal" to "stm32" in documentation and everywhere else.
|
|
|
|
|
|
|
|
|
|
|
|
Without this the pass-through will pause for 1 second at each character.
|
|
|
|
|
|
|
|
State that this doc describes generic, "core" MicroPython functionality,
any particular port may diverge in both directions, by both omitting
some functionality, and adding more, both cases described outside the
generic documentation.
|
|
Describe that the only portable way to deal with addresses is by using
getaddrinfo(). Describe that some ports may support tuple addresses using
"socket" module (vs "usocket" of native MicroPython).
|
|
It's too minor a point to start the module description with it.
|
|
This clarifies return values and the handling of invalid (e.g. newline)
characters.
Encoding conforms to RFC 3548, but decoding does not, as it ignores invalid
characters in base64 input. Instead, it conforms to MIME handling of base64
(RFC 2045).
Note that CPython doesn't document handling of invalid characters in
a2b_base64() docs:
https://docs.python.org/3/library/binascii.html#binascii.a2b_base64 , so
we specify it more explicitly than it, based on CPython's actual behavior
(with which MicroPython now compliant).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|