On microbit.org, in Reference and the MicroPython repo, code samples consistently use random over urandom.
We never use (u)time but it should probably be consistent between the two.
There are also some modules that we don’t yet have docs for as their stubs are from typeshed that also have u and non-u versions (array, collections, errno).
I think we should consistently prefer foo over ufoo.
This doesn't affect what code type checks but does affect tools producing docs from these stubs, including the Python Editor V3 API tab.
On microbit.org, in Reference and the MicroPython repo, code samples consistently use random over urandom.
We never use (u)time but it should probably be consistent between the two.
There are also some modules that we don’t yet have docs for as their stubs are from typeshed that also have u and non-u versions (array, collections, errno).
I think we should consistently prefer foo over ufoo.
This doesn't affect what code type checks but does affect tools producing docs from these stubs, including the Python Editor V3 API tab.