micropython-lib/python-stdlib
Damien George 84ba452113 all: Use non-u versions of built-in modules.
This changes almost all uses of "u-module" to just "module" for the
following built-in modules:
- binascii
- collections
- errno
- io
- json
- socket
- struct
- sys
- time

There are some remaining uses of "u-module" naming, for the cases where the
built-in module is extended in Python, eg `python-stdlib/os` uses `uos`.

Also, there are remaining uses of `utime` when non-standard (compared to
CPython) functions are used, like `utime.ticks_ms()`.

Signed-off-by: Damien George <damien@micropython.org>
2024-06-14 10:35:06 +10:00
..
__future__
abc
argparse all: Use non-u versions of built-in modules. 2024-06-14 10:35:06 +10:00
base64
binascii all: Use non-u versions of built-in modules. 2024-06-14 10:35:06 +10:00
bisect
cmd
collections
collections-defaultdict
contextlib
copy all: Use non-u versions of built-in modules. 2024-06-14 10:35:06 +10:00
curses.ascii
datetime
errno
fnmatch
functools
gzip
hashlib
hashlib-core
hashlib-sha224
hashlib-sha256
hashlib-sha384
hashlib-sha512
heapq
hmac
html
inspect
io
itertools
keyword
locale
logging
operator
os
os-path
pathlib
pickle
pkg_resources all: Use non-u versions of built-in modules. 2024-06-14 10:35:06 +10:00
pkgutil
pprint
quopri
random
shutil
ssl
stat
string
struct
tarfile
tarfile-write
tempfile
textwrap
threading
time
traceback
types
unittest
unittest-discover
uu
venv
warnings
zlib
README.md

README.md

CPython Standard Library

The packages in this directory aim to provide compatible implementations of modules from the Python Standard Library, with the goal of allowing existing Python code to run un-modified on MicroPython.

Implementation

Many packages are implemented in pure Python, often based on the original CPython implementation. (e.g. collections.defaultdict)

Some packages are based on or extend from the built-in "micro" modules in the MicroPython firmware, providing additional functionality that didn't need to be written in C (e.g. collections, socket, struct).

Future plans (ideas for contributors):

  • Add README.md to each library explaining compatibility and limitations.