TW
@t-pi IIRC you did some work on this. should this ticket be closed or is there remaining work to do?
needs more work... / needs checking again.
If we add that, we also want to exclude it from being packaged via a `MANIFEST.in` entry.
Until we have a prettier way like described above, direct memory access via `machine.mem32` can be used, see there: https://github.com/ThomasWaldmann/py-esp32-ulp/blob/master/examples/counter.py
The place where it currently usually runs out of memory is a list comprehension doing a transformation - from A) a list of strings (source lines, comments already were removed)...
Sorry, but I can't help you with this. Although I started py-esp32-ulp, I did not practically use it much myself.
Ah, good idea. I don't really like `unittest`, but guess it's better than nothing.
It would be good to have a test in `borg.testsuite.archiver` that checks if the new code works correctly. See the other tests you already see there about how this could...
IIRC `borg create --stats` already outputs some timing stats, do the new stats in a similar way concerning units and precision. Testings the timing stats of course can not be...