Monotonic ns improvement; time.sleep rounds to nearest msec #2601
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.

Fixes #2334. Fixes #2508.
time.monotonic_ns()to microseconds on all ports. I need some rough timing values that were more granular than milliseconds.time.sleep()to the nearest millisecond. Tested time.sleep() rounds down to next lower millisecond #2508 sample program and now get 100 Hz as intended.time.monotonic_ns()andtime.sleep()should still not be used for precise timing, but this makes them more useful than they were before.Note that
time.monotonic()still increases only on milliseconds. It was not worth improving due to the low precision of 30-bit floats.