suspect-devices/circuitpython/py/compile.c, branch 6.0.x

remove unnecessary board configuration and address feedback

2020-10-12T05:42:59+00:00

update async tests with less upython workaround and more cpython compatibility

2020-10-11T06:39:32+00:00

i do not know if this is needed but this is not the vm i use anymore

2020-10-10T22:45:08+00:00

async def syntax rigor and await magic method

2020-10-10T22:45:08+00:00

Some examples of improved compliance with CPython that currently have divergent behavior in CircuitPython are listed below: * yield from is not allowed in async methods ``` >>> async def f(): ... yield from 'abc' ... Traceback (most recent call last): File "", line 2, in f SyntaxError: 'yield from' inside async function ``` * await only works on awaitable expressions ``` >>> async def f(): ... await 'not awaitable' ... >>> f().send(None) Traceback (most recent call last): File "", line 1, in File "", line 2, in f AttributeError: 'str' object has no attribute '__await__' ``` * only __await__()able expressions are awaitable Okay this one actually does not work in circuitpython at all today. This is how CPython works though and pretending __await__ does not exist will only bite users who write both. ``` >>> class c: ... pass ... >>> def f(self): ... yield ... yield ... return 'f to pay respects' ... >>> c.__await__ = f # could just as easily have put it on the class but this shows how it's wired >>> async def g(): ... awaitable_thing = c() ... partial = await awaitable_thing ... return 'press ' + partial ... >>> q = g() >>> q.send(None) >>> q.send(None) >>> q.send(None) Traceback (most recent call last): File "", line 1, in StopIteration: press f to pay respects ```

Merge pull request #3222 from WarriorOfWire/pick_micropython

2020-07-29T17:54:37+00:00

py/compile: Don't await __aiter__ special method in async-for.

py/compile: Don't await aiter special method in async-for.

2020-07-25T05:55:37+00:00

MicroPython's original implementation of __aiter__ was correct for an earlier (provisional) version of PEP492 (CPython 3.5), where __aiter__ was an async-def function. But that changed in the final version of PEP492 (in CPython 3.5.2) where the function was changed to a normal one. See https://www.python.org/dev/peps/pep-0492/#why-aiter-does-not-return-an-awaitable See also the note at the end of this subsection in the docs: https://docs.python.org/3.5/reference/datamodel.html#asynchronous-iterators And for completeness the BPO: https://bugs.python.org/issue27243 To be consistent with the Python spec as it stands today (and now that PEP492 is final) this commit changes MicroPython's behaviour to match CPython: __aiter__ should return an async-iterable object, but is not itself awaitable. The relevant tests are updated to match. See #6267.

require async for and async with to actually be in an async def method instead of just a generator

2020-07-25T02:47:34+00:00

add coroutine behavior for generators

2020-07-24T03:40:16+00:00

coroutines don't have __next__; they also call themselves coroutines. This does not change the fact that `async def` methods are generators, but it does make them behave more like CPython.

Add license to some obvious files.

2020-07-06T18:16:25+00:00

compile: Give a proper error on 'async with'/'async for' outside 'async def'

2020-03-01T15:40:43+00:00

A simple reproducer is: async for x in():x