Round 2: I’ve posted PR peps#4928 with edits incorporating feedback so far. The implementation has also been updated. short summary:
I dropped the us format in favor of just ns (now using decimal seconds) and iso options. (trivial to add ms and us as well but I don’t see a point in the complexity)
no_timestamp= was renamed to timestamps= in the traceback module APIs and I did wind up going with the tri-state as I came up with a reason why someone might want it.
Various clarifications that came up here that needed recording as more detail or recording either as rejected ideas or open issues (and sometimes both… rejected, but open to exploring, deferring? etc)
sys.monitoring - I dug into that a bit more and describe how it could be used and what it would require… which led to me deciding that was a rejected ideas piece more so than open issue: The RAISE event fires too often, the call overhead on all of those events is high, and it’d involve additional memory allocations and potentially collectable objects created upon every raise.
Lets please keep non-docs editorial discussion here rather than as PR comments. Far more details in the PEP update itself. Please read it. I’ll reply here once it has merged and published. For now, see the PR.