Andrew Leech

* As expected, printing a local variable fails. * breakpoints seem to be stopped on the previous line... breaking on a function name `main` didn't work (presumably because it tried...

FYI I've also got a recent open PR to add a `time` module with `monotonic` in https://github.com/micropython/micropython-lib/pull/502 It'd certainly be trivial to merge them eventually. It's probably worth you adding...

In micropython, the C implementation of builtins are in the `u` modules, eg `uos`, `ucollections`. These are automatically shadowed to the non-u names if there's no other non-u implementation on...

> I think you meant from `utime import *` now that makes sense yes. Ah geez sorry for the confusion, I missed the unwanted autocorrect!

Thanks for this, I agree the existing `logging` module is barely more than something to satify an import in existing libraries. In other projects I've also extended this library to...

With the `CircularFileHandler`, was there a particular reason you chose to start rewriting over the same file in a circular fashion rather than rotating to a second file instead like...

I've just had a chat with others and there's a guidance that everything in `python-stdlib` is expected to match cpython versions of the library, or at least be a subset...

It does go both ways though, I'm certainly very guilty of throwing things up in PR's without tests, docs or even a suitable description sometimes... because I'm in a rush...

On review I've renamed this to `micropython-lib/python-stdlib/time/time.py` to act as a wrapper for `utime` - so this should now work fairly seamlessly for use porting other library with many/most use...

Thanks for this @robert-hh and @omogenot. I was keen to see this happen, but between not having any stm&wiznet hardware to develop against and too many in-progress projects/pr's already it...