Skip to content

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

LamentXU123
Copy link
Contributor

@LamentXU123 LamentXU123 commented Jun 18, 2025

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/

@LamentXU123 LamentXU123 changed the title Some doc improvements in lib UUID Attaching RFC links in UUID docs Jun 19, 2025
@picnixz picnixz added the needs backport to 3.14 bugs and security fixes label Jun 19, 2025
@picnixz
Copy link
Member

picnixz commented Jun 19, 2025

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

@LamentXU123
Copy link
Contributor Author

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

@LamentXU123 LamentXU123 changed the title Attaching RFC links in UUID docs gh-89083Attaching RFC links in UUID docs Jun 19, 2025
@LamentXU123 LamentXU123 changed the title gh-89083Attaching RFC links in UUID docs gh-89083 Attaching RFC links in UUID docs Jun 19, 2025
@picnixz picnixz changed the title gh-89083 Attaching RFC links in UUID docs gh-89083: Attaching RFC links in UUID docs Jun 19, 2025
Comment on lines +199 to +201
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
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaiting review docs Documentation in the Doc dir needs backport to 3.14 bugs and security fixes skip news
Projects
Status: Todo
Development

Successfully merging this pull request may close these issues.

3 participants