6364401666
This implements .pend_throw(exc) method, which sets up an exception to be triggered on the next call to generator's .__next__() or .send() method. This is unlike .throw(), which immediately starts to execute the generator to process the exception. This effectively adds Future-like capabilities to generator protocol (exception will be raised in the future). The need for such a method arised to implement uasyncio wait_for() function efficiently (its behavior is clearly "Future" like, and normally would require to introduce an expensive Future wrapper around all native couroutines, like upstream asyncio does). py/objgenerator: pend_throw: Return previous pended value. This effectively allows to store an additional value (not necessary an exception) in a coroutine while it's not being executed. uasyncio has exactly this usecase: to mark a coro waiting in I/O queue (and thus not executed in the normal scheduling queue), for the purpose of implementing wait_for() function (cancellation of such waiting coro by a timeout). |
||
|---|---|---|
| .. | ||
| basics | ||
| bench | ||
| cmdline | ||
| cpydiff | ||
| extmod | ||
| feature_check | ||
| float | ||
| import | ||
| inlineasm | ||
| io | ||
| jni | ||
| micropython | ||
| misc | ||
| net_hosted | ||
| net_inet | ||
| pyb | ||
| pybnative | ||
| stress | ||
| thread | ||
| unicode | ||
| unix | ||
| wipy | ||
| pyboard.py | ||
| README | ||
| run-bench-tests | ||
| 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.