GitLab

Too big positive, or too big negative offset values could lead to overflow
and address space wraparound and thus access to unrelated areas of memory
(a security issue).

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.

Calls out to Zephyr's shell, submodule "net", command "iface", and shows
network interface information (if CONFIG_NET_SHELL is enabled).

The original issue leading to crash on startup if no default network
interface was presented, was resolved some time ago.

Note that this enables generic networking subsystem, not networking
on Carbon.

Was changed to "sa_family" for POSIX compatibility.

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).

This implementation ignores invalid characters in the input. This allows
it to decode the output of b2a_base64, and also mimics the behavior of
CPython.

The value of 0 can't be used because otherwise mp_binary_get_size will let
a null byte through as the type code (intepreted as byterray).  This can
lead to invalid type-specifier strings being let through without an error
in the struct module, and even buffer overruns.

This makes the -d commandline argument usable again.
Pass empty string as parent name as listing starts from the root.

As required for zephyr.stack_analyze().

current_tid() returns current thread ID. stacks_analyze() calls
k_call_stacks_analyze() which, with CONFIG_INIT_STACKS enabled,
will print stack usage for some well-known threads in the system.

Behaviour is as per CPython but only the binary form is implemented here.
A test is included.

It enables all the DEBUG_printf outputs in the py/ source code.

Without bugfix:

    struct.pack('>Q', 16)
    b'\x00\x00\x00\x10\x00\x00\x00\x00'

With bugfix:

    struct.pack('>Q', 16)
    b'\x00\x00\x00\x00\x00\x00\x00\x10'

  - Changed: ValueError, TypeError, NotImplementedError
  - OSError invocations unchanged, because the corresponding utility
    function takes ints, not strings like the long form invocation.
  - OverflowError, IndexError and RuntimeError etc. not changed for now
    until we decide whether to add new utility functions.

Implemented as a new MP_UNARY_OP. This patch adds support lists, dicts and
instances.

$(TOP) is defined in py/mkenv.mk and should be used to refer to the top
level of this repository.

The main case to catch is invalid types for the containment operator, of
the form str.__contains__(non-str).

Accesses recv_q, accept_q directly in net_context.

This works for Unix and similar ports so far.

For some reason, with the latest Zephyr master, running just "make" led
to executing Zephyr's "qemu" target.

"STATIC inline" can expand to "inline" if STATIC is defined to nothing, and
this case can lead to link errors.

Allows to join multicast groups.

There were several different spellings of MicroPython present in comments,
when there should be only one.

WiFi mode selection happens on the level of individual interfaces.