bpo-33640, uuid.UUID doc: document endian of bytes parameter (GH-7263)

The bytes parameter uses big endian.
This commit is contained in:
Farhaan Bukhsh 2018-06-04 12:59:00 +05:30 committed by Victor Stinner
parent 88cc339ee3
commit b75ec08567
1 changed files with 7 additions and 6 deletions

View File

@ -45,12 +45,13 @@ which relays any information about the UUID's safety, using this enumeration:
.. class:: UUID(hex=None, bytes=None, bytes_le=None, fields=None, int=None, version=None, *, is_safe=SafeUUID.unknown)
Create a UUID from either a string of 32 hexadecimal digits, a string of 16
bytes as the *bytes* argument, a string of 16 bytes in little-endian order as
the *bytes_le* argument, a tuple of six integers (32-bit *time_low*, 16-bit
*time_mid*, 16-bit *time_hi_version*, 8-bit *clock_seq_hi_variant*, 8-bit
*clock_seq_low*, 48-bit *node*) as the *fields* argument, or a single 128-bit
integer as the *int* argument. When a string of hex digits is given, curly
braces, hyphens, and a URN prefix are all optional. For example, these
bytes in big-endian order as the *bytes* argument, a string of 16 bytes in
little-endian order as the *bytes_le* argument, a tuple of six integers
(32-bit *time_low*, 16-bit *time_mid*, 16-bit *time_hi_version*,
8-bit *clock_seq_hi_variant*, 8-bit *clock_seq_low*, 48-bit *node*) as the
*fields* argument, or a single 128-bit integer as the *int* argument.
When a string of hex digits is given, curly braces, hyphens,
and a URN prefix are all optional. For example, these
expressions all yield the same UUID::
UUID('{12345678-1234-5678-1234-567812345678}')