Force UUIDv1 to use a clock sequence storage (RFC 4122)

[contact2]

BPO	44620

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = None
created_at = <Date 2021-07-13.11:15:00.340>
labels = ['type-bug', 'library', '3.9', '3.10', '3.11']
title = 'UUIDv1 is not RFC 4122 compliant'
updated_at = <Date 2022-01-15.17:12:15.334>
user = 'https://bugs.python.org/contact2'

bugs.python.org fields:

activity = <Date 2022-01-15.17:12:15.334>
actor = 'iritkatriel'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2021-07-13.11:15:00.340>
creator = 'contact2'
dependencies = []
files = []
hgrepos = []
issue_num = 44620
keywords = []
message_count = 1.0
messages = ['397392']
nosy_count = 1.0
nosy_names = ['contact2']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue44620'
versions = ['Python 3.9', 'Python 3.10', 'Python 3.11']

Linked PRs

• gh-88786: Update uuid.uuid1() in uuid module to meet RFC4122 #124571

[contact2]

Section 4.1.5 of RFC 4122 says the following about Clock Sequence:

If the clock is set backwards, or might have been set backwards
(e.g., while the system was powered off), and the UUID generator can
not be sure that no UUIDs were generated with timestamps larger than
the value to which the clock was set, then the clock sequence has to
be changed. If the previous value of the clock sequence is known, it
can just be incremented; otherwise it should be set to a random or
high-quality pseudo-random value.

However, the current implementation increments the timestamp and not the clock sequence. Ref:

cpython/Lib/uuid.py

Lines 689 to 690 in bb3e0c2

	if _last_timestamp is not None and timestamp <= _last_timestamp:
	timestamp = _last_timestamp + 1