a6dee730f3
It's needed because different LIBC implementation use different shared library names, so this module abstracts operation of finding the correct one. Default search order: 1. libc.so. This is usually doesn't exist, but user can create such symlink, and it will be used fast. 2. libc.so.0, as used by current uClibc versions. 3. libc.so.6, as used by current Glibc versions. uClibc is tried first because system where it is used are usually underpowered to do array of attempts. User can also override default search names by calling _libc.set_names(), (which should be called before importing any other modules). |
||
|---|---|---|
| _libc | ||
| abc | ||
| base64 | ||
| binascii | ||
| binhex | ||
| bisect | ||
| calendar | ||
| collections | ||
| collections.defaultdict | ||
| collections.deque | ||
| copy | ||
| csv | ||
| datetime | ||
| dbm | ||
| email.charset | ||
| email.encoders | ||
| email.errors | ||
| email.feedparser | ||
| email.header | ||
| email.internal | ||
| email.message | ||
| email.parser | ||
| email.utils | ||
| errno | ||
| fcntl | ||
| fnmatch | ||
| functools | ||
| getopt | ||
| getpass | ||
| glob | ||
| gzip | ||
| hashlib | ||
| heapq | ||
| html/html | ||
| html.entities | ||
| http.client | ||
| io | ||
| ipaddress | ||
| itertools | ||
| json | ||
| keyword | ||
| logging | ||
| mailbox | ||
| mimetypes | ||
| multiprocessing | ||
| optparse | ||
| os | ||
| os.path | ||
| pickle | ||
| posixpath | ||
| pprint | ||
| pty | ||
| queue | ||
| quopri | ||
| random | ||
| re-pcre | ||
| reprlib | ||
| sched | ||
| select | ||
| shelve | ||
| shlex | ||
| shutil | ||
| socket | ||
| sqlite3 | ||
| stat | ||
| string | ||
| subprocess | ||
| tarfile | ||
| tempfile | ||
| test.support | ||
| timeit | ||
| traceback | ||
| types | ||
| unittest | ||
| urllib | ||
| urllib.parse | ||
| uu | ||
| warnings | ||
| zipfile | ||
| .gitignore | ||
| Makefile | ||
| README.md | ||
| make_metadata.py | ||
README.md
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
micropython-lib is highly experimental community project.
Please help to drive it to just "expiremental" state by testing
provided packages with MicroPython.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
micropython-lib
micropython-lib is a project to develop non-monolothic standard library for MicroPython. Each module or package is available as a seprate distribution package from PyPI. Modules either written from scratch or ported from CPython. Note that main target of micropython-lib is so far "Unix" port of MicroPython. Actual requirements vary per module (basicly, if module is not related to I/O, it should work without problem on baremetal ports too).
Usage
micropython-lib packages are published on PyPI (Python Package Index), standard Python community package repository: http://pypi.python.org/ . You can search for MicroPython related packages, read additional info, etc.
To install packages from PyPI for usage on your local system, use "pip-micropython" tool, which is a simple wrapper around a standard "pip" tool, which is used to install package for CPython. "pip-micropython" tool can be found in "tools" subdirectory of the main MicroPython repository (https://github.com/micropython/micropython). Just install "pip-micropython" script somewhere on your PATH.
Afterwards, just use pip-micropython in a way similar to pip:
$ pip-micropython install micropython-copy
$ micropython
>>> import copy
>>> copy.copy([1, 2, 3])
[1, 2, 3]
Review pip-micropython source code for more info.
Development
To install modules during development, use "make install". By default, it will install all available packages. You can pass MOD= parameter to install specific module.
Links
More info:
- https://github.com/micropython/micropython/issues/405
- http://forum.micropython.org/viewtopic.php?f=5&t=70
Basic guidelines for installing packages from PyPI: