4c93955b7b
Instances of the slice class are passed to __getitem__() on objects when the user indexes them with a slice. In practice the majority of the time (other than passing it on untouched) is to work out what the slice means in the context of an array dimension of a particular length. Since Python 2.3 there has been a method on the slice class, indices(), that takes a dimension length and returns the real start, stop and step, accounting for missing or negative values in the slice spec. This commit implements such a indices() method on the slice class. It is configurable at compile-time via MICROPY_PY_BUILTINS_SLICE_INDICES, disabled by default, enabled on unix, stm32 and esp32 ports. This commit also adds new tests for slice indices and for slicing unicode strings. |
||
|---|---|---|
| .. | ||
| basics | ||
| cmdline | ||
| cpydiff | ||
| extmod | ||
| feature_check | ||
| float | ||
| import | ||
| inlineasm | ||
| internal_bench | ||
| io | ||
| jni | ||
| micropython | ||
| misc | ||
| net_hosted | ||
| net_inet | ||
| perf_bench | ||
| pyb | ||
| pybnative | ||
| qemu-arm | ||
| stress | ||
| thread | ||
| unicode | ||
| unix | ||
| wipy | ||
| README | ||
| run-internalbench.py | ||
| run-natmodtests.py | ||
| run-perfbench.py | ||
| run-tests | ||
| run-tests-exp.py | ||
| run-tests-exp.sh | ||
This directory contains tests for various functionality areas of MicroPython. To run all stable tests, run "run-tests" script in this directory. Tests of capabilities not supported on all platforms should be written to check for the capability being present. If it is not, the test should merely output 'SKIP' followed by the line terminator, and call sys.exit() to raise SystemExit, instead of attempting to test the missing capability. The testing framework (run-tests in this directory, test_main.c in qemu_arm) recognizes this as a skipped test. There are a few features for which this mechanism cannot be used to condition a test. The run-tests script uses small scripts in the feature_check directory to check whether each such feature is present, and skips the relevant tests if not. When creating new tests, anything that relies on float support should go in the float/ subdirectory. Anything that relies on import x, where x is not a built-in module, should go in the import/ subdirectory.