suspect-devices/circuitpython/tests/basics, branch 6.0.0-alpha.0

Fix up end of file and trailing whitespace.

2020-06-03T09:56:35+00:00

This can be enforced by pre-commit, but correct it separately to make it easier to review.

tests: Add .exp files for basics/parser and import/import_override.

2020-04-01T21:31:33+00:00

Because CPython 3.8.0 now produces different output: - basics/parser.py: CPython does not allow '\\\n' as input. - import/import_override: CPython imports _io.

tests/basics: Provide .exp files for generator tests that fail PEP479.

2020-03-31T22:27:10+00:00

PEP479 (see https://www.python.org/dev/peps/pep-0479/) prohibited raising StopIteration from within a generator (it is turned into a RuntimeError). This behaviour was introduced in Python 3.5 and in 3.7 was made compulsory. Until uPy implements PEP479, this patch adds .py.exp files for the relevant tests so they can be run under Python 3.7.

tests: Modify tests that print repr of an exception with 1 arg.

2020-03-31T22:27:10+00:00

In Python 3.7 the behaviour of repr() of an exception with one argument changed: it no longer prints a trailing comma in the argument list. See https://bugs.python.org/issue30399 This patch modifies tests that rely on this behaviour to not rely on it. And the python34.py test is updated to include a test for this behaviour with a .exp file.

tests/basics/int_big_error.py: Use bytearray to test for int overflow.

2020-03-31T22:27:10+00:00

In Python 3.7 "1 >> (big int)" is now allowed, it no longer raises an OverflowError. So use bytearray to test big-int conversion overflow.

tests/basics/set_pop.py: Sort set before printing for consistent output.

2020-03-31T22:27:10+00:00

Update tests

2020-03-10T02:13:33+00:00

* string_pep498_fstring.py: Not compatible with python3.5 * cmd_parsetree.py: enumerated constants changed

lexer: catch concatenation of f'' and '' strings

2020-03-09T14:03:25+00:00

This turns the "edge case" into a parse-time error.

Address dpgeorge feedback - largely simplifications

2020-03-09T13:16:07+00:00

py: Implement partial PEP-498 (f-string) support

2020-03-09T13:16:07+00:00

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](https://github.com/micropython/micropython/commit/534b7c368dc2af7720f3aaed0c936ef46d773957), two side effects emerge: - All strings with at least one f-string portion are concatenated into a single literal which *must* be run through `String.format()` wholesale, and: - Concatenation of a raw string with interpolation characters with an f-string will cause `IndexError`/`KeyError`, which is both different from CPython *and* different from the corner case mentioned in the PEP (which gave an example of the following:) ```python x = 10 y = 'hi' assert ('a' 'b' f'{x}' '{c}' f'str<{y:^4}>' 'd' 'e') == 'ab10{c}str< hi >de' ``` The above-linked commit detailed a pretty solid case for leaving string concatenation in the lexer rather than putting it in the parser, and undoing that decision would likely be disproportionately costly on resources for the sake of a probably-low-impact corner case. An alternative to become complaint with this corner case of the PEP would be to revert to string concatenation in the parser *only when an f-string is part of concatenation*, though I've done no investigation on the difficulty or costs of doing this. A decent set of tests is included. I've manually tested this on the `unix` port on Linux and on a Feather M4 Express (`atmel-samd`) and things seem sane.