Da

✏️ Editing: _compat.cpython-310.pyc

����$
x`G����������������������@���s����d�Z�ddlZddlZddlZejd�dk�r(dd��ZeejfZe	fZ
dZdZdZ
nd	d��ZefZefZ
d
ZdZdZ
eed�Ze
o@eZdd
��Zdd��Zdd��Zdd��Zdd��Zdd��Zddd�ZdS�)z�
Support functions for dealing with differences in platforms, including Python
versions and implementations.

This file should have no imports from the rest of zope.interface because it is
used during early bootstrapping.
�����N����c�����������������C���s���t�|�t�r	t|��S�td��)Nz(name must be a regular or unicode string)�
isinstance�
basestringZunicode�	TypeError��name��r����8/usr/lib/python3/dist-packages/zope/interface/_compat.py�_normalize_name���s���
r
���Z__builtin__FTc�����������������C���s*���t�|�t�r
t|�d�}�t�|�t�r|�S�td��)N�asciiz)name must be a string or ASCII-only bytes)r����bytes�strr���r���r���r���r	���r
���*���s
���

�builtins�pypy_version_infoc�����������������C���s"���dd�l�}|�tjd�dkd�|��S�)Nr���r���zOnly on Python 2��unittestZskipIf�sys�version_info�Ztest_methodr���r���r���r	����_skip_under_py3k<�������r���c�����������������C���s"���dd�l�}|�tjd�dk�d�|��S�)Nr���r���zOnly on Python 3r���r���r���r���r	����_skip_under_py2A���r���r���c������������������C���s���t�j�d�}�|�dk}|S�)z�
    Return a true value if the C optimizations are required.

This uses the ``PURE_PYTHON`` variable as documented in `_use_c_impl`.
    �PURE_PYTHON�0��os�environ�get)�pure_envZ	require_cr���r���r	����_c_optimizations_requiredF���s���r���c������������������C���s8���t���rdntf}�z	ddlm}�|W�S��|�y���Y�dS�w�)z�
    Return the C optimization module, if available, otherwise
    a false value.

If the optimizations are required but not available, this
    raises the ImportError.

This does not say whether they should be used or not.
    r���r���)�_zope_interface_coptimizationsF)r����ImportErrorZzope.interfacer ���)Zcatch�c_optr���r���r	����_c_optimizations_availableQ���s���
�r#���c������������������C���s���t�j�d�}�|�duo
|�dkS�)z6
    The opposite of `_c_optimizations_required`.
    r���Nr���r���)r���r���r���r	����_c_optimizations_ignoredc���s���r$���c������������������C���s$���t�td�}�t��r
dS�|�rdS�t���S�)z�
    Return a true value if we should attempt to use the C optimizations.

This takes into account whether we're on PyPy and the value of the
    ``PURE_PYTHON`` environment variable, as defined in `_use_c_impl`.
    r���TF)�hasattrr���r���r$���)Zis_pypyr���r���r	����_should_attempt_c_optimizationsk���s���
r&���c��������������������sJ�����p�j���|pt�d�j}���fdd�}|��}�|��d�<��|��d�<�|S�)a��
    Decorator. Given an object implemented in Python, with a name like
    ``Foo``, import the corresponding C implementation from
    ``zope.interface._zope_interface_coptimizations`` with the name
    ``Foo`` and use it instead.

If the ``PURE_PYTHON`` environment variable is set to any value
    other than ``"0"``, or we're on PyPy, ignore the C implementation
    and return the Python version. If the C implementation cannot be
    imported, return the Python version. If ``PURE_PYTHON`` is set to
    0, *require* the C implementation (let the ImportError propagate);
    note that PyPy can import the C implementation in this case (and all
    tests pass).

In all cases, the Python version is kept available. in the module
    globals with the name ``FooPy`` and the name ``FooFallback`` (both
    conventions have been used; the C implementation of some functions
    looks for the ``Fallback`` version, as do some of the Sphinx
    documents).

Example::

@_use_c_impl
        class Foo(object):
            ...
    ����c���������������������s&���t���s�S�t��}�|�s�S�|�}t|����S�)N)r&���r#����getattr)r"���Z__traceback_info__�r����py_implr���r	����	find_impl����s���
z_use_c_impl.<locals>.find_implZPyZFallback)�__name__r����	_getframe�	f_globals)r*���r���Zglobsr+���Zc_implr���r)���r	����_use_c_impl{���s���
r/���)NN)�__doc__r���r����typesr���r
����typeZ	ClassTypeZCLASS_TYPESr���ZSTRING_TYPESZ	_BUILTINSZPYTHON3ZPYTHON2r
���r%���ZPYPYZPYPY2r���r���r���r#���r$���r&���r/���r���r���r���r	����<module>���s4���

📁 Sid Gifari File Manager