GitLab

Here we are assuming that a thumb2 port will have fatfs, which is only
roughly true.  We need a better way of enabling specific raw-code file
readers.

This can then be passed to mp_raw_code_save_file to save a .mpy file.

This change makes the code behave how it was supposed to work when first
written.  The avail_slot variable is set to the first free slot when
looking for a key (which would come from deleting an entry).  So it's
more efficient (for subsequent lookups) to insert a new key into such a
slot, rather than the very last slot that was searched.

Also provide workarounds, link to other revelant sections,
and fix some typos.

- The link establishment timeout is infinite by default
- Fix typo in notes about the auth kwarg

It can change asynchronously.

Will be included only when MICROPY_PY_MATH_SPECIAL_FUNCTIONS is enabled.

Also covers cmath module (but only log10 is there at the moment).

Parameter lists can't be nested so there is no need to save the global
state when compiling them.

Underlyingly, uses standard POSIX poll() for portability.

In new hardware API, these classes implement master modes of interfaces,
and "mode" parameter is not accepted. Trying to implement new HW API
in terms of older pyb module leaves variuos corner cases:

In new HW API, I2C(1) means "I2C #1 in master mode" (? depends on
interpretation), while in old API, it means "I2C #1, with no settings
changes".

For I2C class, it's easy to make mode optional, because that's last
positional param, but for SPI, there's "baudrate" after it (which
is inconsistent with I2C, which requires "baudrate" to be kwonly-arg).

This fixes the build after changes in [66fd3e4a] and [3a6b3d23]

Removes FFI dependency, instead uses builtin os module. Thus can work on
systems where dynamic library loading is not available.

Dependency of upip.

Dependency of upip.

This also unbreaks "make minimal".

It's safer to define it where it's used, defining it for all source files
may lead to hard to diagnose conflicts in corner cases.

MICROPY_PERSISTENT_CODE must be enabled, and then enabling
MICROPY_PERSISTENT_CODE_LOAD/SAVE (either or both) will allow loading
and/or saving of code (at the moment just bytecode) from/to a .mpy file.

Main changes when MICROPY_PERSISTENT_CODE is enabled are:

- qstrs are encoded as 2-byte fixed width in the bytecode
- all pointers are removed from bytecode and put in const_table (this
  includes const objects and raw code pointers)

Ultimately this option will enable persistence for not just bytecode but
also native code.

Contains just argument names at the moment but makes it easy to add
arbitrary constants.