unsupported #%ˆl–ß=¿JJj"Tâ�và¸&TÅ£Ê ƒh¹ÉÀÍ%0 'ˆÁÊ „›?ÉÀÍ?÷'a ´i¼jã@sRdZddlZddlZddlmZdZejdvr8dZZn ddlZe  ¡Z e dkZe dkZd Z dZ erld Z d Z gd ¢\Z ZZZeZeZGd d„deƒZGdd„dƒZdd„Zdd„Zdd„Zdd„Zdd„Zdd„Zdd„Zdd „Zd!d"„Zd#d$„Z d%d&„Z!d'd(„Z"z*ddl#Z#e$e#d)dƒZ%e$e#d*dƒZ&e#j'Z(Wn$e)�yPdZ#dZ%dZ&dZ(Yn0d+d,„Z*d-d.„Z+d/d0„Z,d1d2„Z-e�r‚eegZ.nFejd3k�ršeee gZ.n.ejd4k�r¬gZ.ne�rºe gZ.neeee egZ.ej/d5k�ràe+ge.Z0nej/d6k�røe,ge.Z0ne.Z0da1d7d8„Z2da3dEd9d:„Z4d;d<„Z5d=d>„Z6d?d@„Z7edAƒZ8edBƒZ9edCƒZ:edDƒZ;dS)FaQUUID objects (universally unique identifiers) according to RFC 4122. This module provides immutable UUID objects (class UUID) and the functions uuid1(), uuid3(), uuid4(), uuid5() for generating version 1, 3, 4, and 5 UUIDs as specified in RFC 4122. If all you want is a unique ID, you should probably call uuid1() or uuid4(). Note that uuid1() may compromise privacy since it creates a UUID containing the computer's network address. uuid4() creates a random UUID. Typical usage: >>> import uuid # make a UUID based on the host ID and current time >>> uuid.uuid1() # doctest: +SKIP UUID('a8098c1a-f86e-11da-bd1a-00112444be1e') # make a UUID using an MD5 hash of a namespace UUID and a name >>> uuid.uuid3(uuid.NAMESPACE_DNS, 'python.org') UUID('6fa459ea-ee8a-3ca4-894e-db77e160355e') # make a random UUID >>> uuid.uuid4() # doctest: +SKIP UUID('16fd2706-8baf-433b-82eb-8c7fada847da') # make a UUID using a SHA-1 hash of a namespace UUID and a name >>> uuid.uuid5(uuid.NAMESPACE_DNS, 'python.org') UUID('886313e1-3b8a-5372-9b90-0c9aee199e5d') # make a UUID from a string of hex digits (braces and hyphens ignored) >>> x = uuid.UUID('{00010203-0405-0607-0809-0a0b0c0d0e0f}') # convert a UUID to a string of hex digits in standard form >>> str(x) '00010203-0405-0607-0809-0a0b0c0d0e0f' # get the raw 16 bytes of the UUID >>> x.bytes b'\x00\x01\x02\x03\x04\x05\x06\x07\x08\t\n\x0b\x0c\r\x0e\x0f' # make a UUID from a 16-byte string >>> uuid.UUID(bytes=x.bytes) UUID('00010203-0405-0607-0809-0a0b0c0d0e0f') éN)ÚEnumzKa-Ping Yee )Úwin32ÚdarwinFZAIXZLinuxó:ó.T)zreserved for NCS compatibilityzspecified in RFC 4122z$reserved for Microsoft compatibilityzreserved for future definitionc@seZdZdZdZdZdS)ÚSafeUUIDréÿÿÿÿN)Ú__name__Ú __module__Ú __qualname__ÚsafeZunsafeÚunknown©rrú/usr/lib64/python3.9/uuid.pyrNsrc@s:eZdZdZdZd=ejdœdd„Zdd„Zd d „Z d d „Z d d„Z dd„Z dd„Z dd„Zdd„Zdd„Zdd„Zdd„Zdd„Zedd „ƒZed!d"„ƒZed#d$„ƒZed%d&„ƒZed'd(„ƒZed)d*„ƒZed+d,„ƒZed-d.„ƒZed/d0„ƒZed1d2„ƒZed3d4„ƒZed5d6„ƒZ ed7d8„ƒZ!ed9d:„ƒZ"ed;d<„ƒZ#dS)>ÚUUIDa¦ Instances of the UUID class represent UUIDs as specified in RFC 4122. UUID objects are immutable, hashable, and usable as dictionary keys. Converting a UUID to a string with str() yields something in the form '12345678-1234-1234-1234-123456789abc'. The UUID constructor accepts five possible forms: a similar string of hexadecimal digits, or a tuple of six integer fields (with 32-bit, 16-bit, 16-bit, 8-bit, 8-bit, and 48-bit values respectively) as an argument named 'fields', or a string of 16 bytes (with all the integer fields in big-endian order) as an argument named 'bytes', or a string of 16 bytes (with the first three fields in little-endian order) as an argument named 'bytes_le', or a single 128-bit integer as an argument named 'int'. UUIDs have these read-only attributes: bytes the UUID as a 16-byte string (containing the six integer fields in big-endian byte o