In a fresh WASI build,time.process_time, which should be in seconds, counts 10⁶ times faster thantime.time:

>>> import time>>> time.time(); time.process_time()1708435312.5965584775079350.12>>> time.time(); time.process_time()1708435313.09494614780063256.54>>> time.get_clock_info('process_time')namespace(implementation='clock_gettime(CLOCK_PROCESS_CPUTIME_ID)', monotonic=True, adjustable=False, resolution=1e-09)

It looks likeWASI might removeCLOCK_PROCESS_CPUTIME_ID. Should we wait for that? Remove it from Python sooner? Work around the issue?

(Codespaces has an “unexpected error” for me right now, so I built the container from.devcontainer/Dockerfile directly. Hope that doesn't affect the result.)

Linked PRs

• gh-115714: Don't use CLOCK_PROCESS_CPUTIME_ID and times() on WASI #115757