MicroPython Forum (Archive)

Check these files for my custom 1MB firmware: https://github.com/kevinkk525/pysmartno ... artnode_1M

ok thanks for the info. The current uasyncio implementation is CPython compatible almost everywhere because this time it was a basic requirement to be CPython compatible. But it does not distinguish between a coroutine and a generator. But from the top of my head I can't think of how someone would a...

lol ok.. interesting. Why didn't they just use the "official" uasyncio module? .. (sorry I know you're not the right person for this question)

CircuitPython has no asyncio support afaik, why would they need a distinction between coroutines and generators?

I don't know a better way either. It's probably not easy because of the changes to keep everything "micro".

The difference is that Christian's approach doesn't execute the function and purely inspects it "untouched", while pythoncoder's approach executes the function and then checks if the returned type is an active generator function which can be passed to uasyncio.create_task(). Pythoncoder's approach i...

You are missing an __init__.py in both the root and the ht16k33 directory. Then it should work.
(btw, if it works in CPython, it'll work in micropython)

In my project I import multiple modules. After each import statement I call gc.collect() to free all the RAM that only was only temporarily used during import. Then I call gc.collect() after creating bigger objects. This ensures that the RAM is as continuously used as possible and the fragmentation ...

I only use "del" in long running loops which occasionally create large temporary data structures. (Afterwards I call gc.collect() to free that RAM). That way those variables don't take up unneccessary RAM. Simple, yet weird example: while True: a={} a.update(await get_results()) await asyncio.sleep(...

Might also be due to socket operations in webrepl making it slower, more complex and more resource hungry?