-
-
Notifications
You must be signed in to change notification settings - Fork 32.2k
gh-89083: Attaching RFC links in UUID docs #135684
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
I won't backport this to 3.13 because the rfc number changed with the addition to v6-8. Can you find the issue where I added 6-8 and use it for this PR please? TiA |
Ofcourse. #89083 |
If *node* is not given, :func:`getnode` is used to obtain the hardware address. | ||
|
||
If *clock_seq* is given, it is used as the sequence number; otherwise a random |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If *node* is not given, :func:`getnode` is used to obtain the hardware address. | |
If *clock_seq* is given, it is used as the sequence number; otherwise a random | |
When *node* is not specified, :func:`getnode` is used to obtain the hardware | |
address as a 48-bit positive integer. When a sequence number *clock_seq* is | |
not specified, a pseudo-random 14-bit positive integer is generated. |
Let's have the same formulation as in UUIDv6.
Add RFC links to the former UUID version and standardize the docs since UUIDv7-8 and nil, max has its RFC links
Skipping news and issues caz this is a doc change :)
📚 Documentation preview 📚: https://cpython-previews--135684.org.readthedocs.build/