According to the RFC, a uuid1 uses a 60-bit 100ns-resolution clock. I found a PR which migrated the implementation from time.time() to time.time_ns() as well (#11189).
uuid1 adds a random sequence (by default), thus I'd expect uuid1 to vary at least as much as time_ns() // 100, but experimentally it does not:
Bug report
According to the RFC, a uuid1 uses a 60-bit 100ns-resolution clock. I found a PR which migrated the implementation from
time.time()
totime.time_ns()
as well (#11189).uuid1 adds a random sequence (by default), thus I'd expect uuid1 to vary at least as much as
time_ns() // 100
, but experimentally it does not:Significant variations beyond the sequence start occurring around 1s on this machine, but even at 1.5 it's far from a guarantee:
Your environment
This issue was observed on a Dell Latitude 5400 (SKU 08B8) with an i5-8365U (x86_64) running Linux Mint 21.1.
It was reproduced on: