golden hour

/opt/alt/python37/lib64/python3.7/site-packages/Crypto/Util/__pycache__

File/Folder	Size	Actions
Counter.cpython-37.opt-1.pyc	3.73 KB
Counter.cpython-37.pyc	3.73 KB
RFC1751.cpython-37.opt-1.pyc	23.1 KB
RFC1751.cpython-37.pyc	23.1 KB
__init__.cpython-37.opt-1.pyc	690 B
__init__.cpython-37.pyc	690 B
_number_new.cpython-37.opt-1.pyc	2.55 KB
_number_new.cpython-37.pyc	2.64 KB
asn1.cpython-37.opt-1.pyc	11.33 KB
asn1.cpython-37.pyc	11.33 KB
number.cpython-37.opt-1.pyc	58.08 KB
number.cpython-37.pyc	58.12 KB
py3compat.cpython-37.opt-1.pyc	3.19 KB
py3compat.cpython-37.pyc	3.19 KB
randpool.cpython-37.opt-1.pyc	2.52 KB
randpool.cpython-37.pyc	2.52 KB
winrandom.cpython-37.opt-1.pyc	231 B
winrandom.cpython-37.pyc	231 B

Edit: py3compat.cpython-37.opt-1.pyc

������cD������������������@���s����d�Z�dZddlZejd�dkr`dd��Zdd��Zd	d
��Zdd��Zejd
�d
krVdd��Zq�dd��Zn(dd��Zdd��Zdd
��Zdd��Zdd��ZdS�)a���Compatibility code for handling string/bytes changes from Python 2.x to Py3k

In Python 2.x, strings (of type ''str'') contain binary data, including encoded
Unicode text (e.g. UTF-8).  The separate type ''unicode'' holds Unicode text.
Unicode literals are specified via the u'...' prefix.  Indexing or slicing
either type always produces a string of the same type as the original.
Data read from a file is always of '''str'' type.

In Python 3.x, strings (type ''str'') may only contain Unicode text. The u'...'
prefix and the ''unicode'' type are now redundant.  A new type (called
''bytes'') has to be used for binary data (including any particular
''encoding'' of a string).  The b'...' prefix allows one to specify a binary
literal.  Indexing or slicing a string produces another string.  Slicing a byte
string produces another byte string, but the indexing operation produces an
integer.  Data read from a file is of '''str'' type if the file was opened in
text mode, or of ''bytes'' type otherwise.

Since PyCrypto aims at supporting both Python 2.x and 3.x, the following helper
functions are used to keep the rest of the library as independent as possible
from the actual Python version.

In general, the code should always deal with binary strings, and use integers
instead of 1-byte character strings.

b(s)
    Take a text string literal (with no prefix or with u'...' prefix) and
    make a byte string.
bchr(c)
    Take an integer and make a 1-character byte string.
bord(c)
    Take the result of indexing on a byte string and make an integer.
tobytes(s)
    Take a text string, a byte string, or a sequence of character taken from
    a byte string and make a byte string.
z$Id$�����N����c�������������C���s���|�S�)N��)�sr���r����H/opt/alt/python37/lib64/python3.7/site-packages/Crypto/Util/py3compat.py�bB���s����r���c�������������C���s���t�|��S�)N)�chr)r���r���r���r����bchrD���s����r���c�������������C���s���t�|��S�)N)�str)r���r���r���r����bstrF���s����r
���c�������������C���s���t�|��S�)N)�ord)r���r���r���r����bordH���s����r�������c�������������C���s ���y
|���d�S����d�|��S�d�S�)Nzlatin-1��)�encode�join)r���r���r���r����tobytesK���s����
r���c�������������C���s"���t�|�t�r|��d�S�d�|��S�d�S�)Nzlatin-1r���)�
isinstancer	���r���r���)r���r���r���r���r���Q���s����

c�������������C���s
���|���d�S�)Nzlatin-1)r���)r���r���r���r���r���W���s����c�������������C���s
���t�|�g�S�)N)�bytes)r���r���r���r���r���Y���s����c�������������C���s ���t�|�t�rt|�d�S�t|��S�d�S�)Nzlatin-1)r���r	���r���)r���r���r���r���r
���[���s����

c�������������C���s���|�S�)Nr���)r���r���r���r���r���`���s����c�������������C���s.���t�|�t�r|�S�t�|�t�r"|��d�S�t|��S�d�S�)Nzlatin-1)r���r���r	���r���)r���r���r���r���r���b���s
����

)	�__doc__Z__revision__�sys�version_infor���r���r
���r���r���r���r���r���r����<module>;���s���