3a7a5ba686
This implements (most of) the PEP-498 spec for f-strings, with two
exceptions:
- raw f-strings (`fr` or `rf` prefixes) raise `NotImplementedError`
- one special corner case does not function as specified in the PEP
(more on that in a moment)
This is implemented in the core as a syntax translation, brute-forcing
all f-strings to run through `String.format`. For example, the statement
`x='world'; print(f'hello {x}')` gets translated *at a syntax level*
(injected into the lexer) to `x='world'; print('hello {}'.format(x))`.
While this may lead to weird column results in tracebacks, it seemed
like the fastest, most efficient, and *likely* most RAM-friendly option,
despite being implemented under the hood with a completely separate
`vstr_t`.
Since [string concatenation of adjacent literals is implemented in the
lexer](
|
||
|---|---|---|
| .. | ||
| basics | ||
| bench | ||
| circuitpython | ||
| 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 | ||
| skip_if.py | ||
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.