2014-10-31 22:21:37 +00:00
|
|
|
:mod:`sys` -- system specific functions
|
|
|
|
=======================================
|
2014-10-31 01:37:19 +00:00
|
|
|
|
|
|
|
.. module:: sys
|
|
|
|
:synopsis: system specific functions
|
|
|
|
|
2017-07-02 13:37:31 +01:00
|
|
|
|see_cpython_module| :mod:`python:sys`.
|
|
|
|
|
2014-10-31 01:37:19 +00:00
|
|
|
Functions
|
|
|
|
---------
|
|
|
|
|
2016-05-01 11:42:36 +01:00
|
|
|
.. function:: exit(retval=0)
|
2014-10-31 01:37:19 +00:00
|
|
|
|
2016-05-01 11:42:36 +01:00
|
|
|
Terminate current program with a given exit code. Underlyingly, this
|
2017-06-27 22:37:47 +01:00
|
|
|
function raise as `SystemExit` exception. If an argument is given, its
|
|
|
|
value given as an argument to `SystemExit`.
|
2014-10-31 01:37:19 +00:00
|
|
|
|
2016-05-01 11:44:06 +01:00
|
|
|
.. function:: print_exception(exc, file=sys.stdout)
|
2014-12-06 22:18:37 +00:00
|
|
|
|
2017-06-27 22:37:47 +01:00
|
|
|
Print exception with a traceback to a file-like object *file* (or
|
|
|
|
`sys.stdout` by default).
|
2014-12-06 22:18:37 +00:00
|
|
|
|
2014-12-19 22:10:38 +00:00
|
|
|
.. admonition:: Difference to CPython
|
2014-12-22 13:42:30 +00:00
|
|
|
:class: attention
|
2014-12-19 22:10:38 +00:00
|
|
|
|
2016-06-10 21:06:56 +01:00
|
|
|
This is simplified version of a function which appears in the
|
|
|
|
``traceback`` module in CPython. Unlike ``traceback.print_exception()``,
|
|
|
|
this function takes just exception value instead of exception type,
|
2017-06-27 22:37:47 +01:00
|
|
|
exception value, and traceback object; *file* argument should be
|
2016-06-18 17:05:50 +01:00
|
|
|
positional; further arguments are not supported. CPython-compatible
|
2016-06-10 21:06:56 +01:00
|
|
|
``traceback`` module can be found in micropython-lib.
|
2014-12-19 22:10:38 +00:00
|
|
|
|
2014-10-31 01:37:19 +00:00
|
|
|
Constants
|
|
|
|
---------
|
|
|
|
|
|
|
|
.. data:: argv
|
|
|
|
|
2016-05-01 11:38:45 +01:00
|
|
|
A mutable list of arguments the current program was started with.
|
2014-10-31 01:37:19 +00:00
|
|
|
|
|
|
|
.. data:: byteorder
|
|
|
|
|
2017-06-27 22:37:47 +01:00
|
|
|
The byte order of the system (``"little"`` or ``"big"``).
|
2014-10-31 01:37:19 +00:00
|
|
|
|
2016-05-01 11:59:34 +01:00
|
|
|
.. data:: implementation
|
|
|
|
|
|
|
|
Object with information about the current Python implementation. For
|
|
|
|
MicroPython, it has following attributes:
|
|
|
|
|
2017-06-27 22:37:47 +01:00
|
|
|
* *name* - string "micropython"
|
|
|
|
* *version* - tuple (major, minor, micro), e.g. (1, 7, 0)
|
2016-05-01 11:59:34 +01:00
|
|
|
|
|
|
|
This object is the recommended way to distinguish MicroPython from other
|
|
|
|
Python implementations (note that it still may not exist in the very
|
|
|
|
minimal ports).
|
|
|
|
|
|
|
|
.. admonition:: Difference to CPython
|
|
|
|
:class: attention
|
|
|
|
|
|
|
|
CPython mandates more attributes for this object, but the actual useful
|
|
|
|
bare minimum is implemented in MicroPython.
|
|
|
|
|
2016-05-01 12:31:08 +01:00
|
|
|
.. data:: maxsize
|
|
|
|
|
|
|
|
Maximum value which a native integer type can hold on the current platform,
|
|
|
|
or maximum value representable by MicroPython integer type, if it's smaller
|
|
|
|
than platform max value (that is the case for MicroPython ports without
|
|
|
|
long int support).
|
|
|
|
|
|
|
|
This attribute is useful for detecting "bitness" of a platform (32-bit vs
|
|
|
|
64-bit, etc.). It's recommended to not compare this attribute to some
|
|
|
|
value directly, but instead count number of bits in it::
|
|
|
|
|
|
|
|
bits = 0
|
|
|
|
v = sys.maxsize
|
|
|
|
while v:
|
|
|
|
bits += 1
|
|
|
|
v >>= 1
|
|
|
|
if bits > 32:
|
|
|
|
# 64-bit (or more) platform
|
|
|
|
...
|
|
|
|
else:
|
|
|
|
# 32-bit (or less) platform
|
|
|
|
# Note that on 32-bit platform, value of bits may be less than 32
|
|
|
|
# (e.g. 31) due to peculiarities described above, so use "> 16",
|
|
|
|
# "> 32", "> 64" style of comparisons.
|
|
|
|
|
2016-05-01 11:32:15 +01:00
|
|
|
.. data:: modules
|
|
|
|
|
|
|
|
Dictionary of loaded modules. On some ports, it may not include builtin
|
|
|
|
modules.
|
|
|
|
|
2014-10-31 01:37:19 +00:00
|
|
|
.. data:: path
|
|
|
|
|
2016-05-01 11:38:45 +01:00
|
|
|
A mutable list of directories to search for imported modules.
|
2014-10-31 01:37:19 +00:00
|
|
|
|
|
|
|
.. data:: platform
|
|
|
|
|
2016-05-01 12:39:38 +01:00
|
|
|
The platform that MicroPython is running on. For OS/RTOS ports, this is
|
|
|
|
usually an identifier of the OS, e.g. ``"linux"``. For baremetal ports it
|
2017-06-27 22:37:47 +01:00
|
|
|
is an identifier of a board, e.g. ``"pyboard"`` for the original MicroPython
|
2016-05-01 12:39:38 +01:00
|
|
|
reference board. It thus can be used to distinguish one board from another.
|
|
|
|
If you need to check whether your program runs on MicroPython (vs other
|
2017-06-27 22:37:47 +01:00
|
|
|
Python implementation), use `sys.implementation` instead.
|
2014-10-31 01:37:19 +00:00
|
|
|
|
|
|
|
.. data:: stderr
|
|
|
|
|
2016-05-01 11:38:45 +01:00
|
|
|
Standard error stream.
|
2014-10-31 01:37:19 +00:00
|
|
|
|
|
|
|
.. data:: stdin
|
|
|
|
|
2016-05-01 11:38:45 +01:00
|
|
|
Standard input stream.
|
2014-10-31 01:37:19 +00:00
|
|
|
|
|
|
|
.. data:: stdout
|
|
|
|
|
2016-05-01 11:38:45 +01:00
|
|
|
Standard output stream.
|
2014-10-31 01:37:19 +00:00
|
|
|
|
|
|
|
.. data:: version
|
|
|
|
|
2016-05-01 11:38:45 +01:00
|
|
|
Python language version that this implementation conforms to, as a string.
|
2014-10-31 01:37:19 +00:00
|
|
|
|
|
|
|
.. data:: version_info
|
|
|
|
|
2016-05-01 11:38:45 +01:00
|
|
|
Python language version that this implementation conforms to, as a tuple of ints.
|