✏️ Editing: _typing.cpython-310.pyc Read Only

����Xai����������������������@���s2���d�Z�ddgZ	�dZerddlmZ�dS�dd��ZdS�)	a;��For neatly implementing static typing in packaging.

`mypy` - the static type analysis tool we use - uses the `typing` module, which
provides core functionality fundamental to mypy's functioning.

Generally, `typing` would be imported at runtime and used in that fashion -
it acts as a no-op at runtime and does not have any run-time overhead by
design.

As it turns out, `typing` is not vendorable - it uses separate sources for
Python 2/Python 3. Thus, this codebase can not expect it to be present.
To work around this, mypy allows the typing import to be behind a False-y
optional to prevent it from running at runtime and type-comments can be used
to remove the need for the types to be accessible directly during runtime.

This module provides the False-y guard in a nicely named fashion so that a
curious maintainer can reach here to read this.

In packaging, all static-typing related imports should be guarded as follows:

from packaging._typing import TYPE_CHECKING

if TYPE_CHECKING:
        from typing import ...

Ref: https://github.com/python/mypy/issues/3216
�
TYPE_CHECKING�castF�����)r���)r���c�����������������C���s���|S�)N��)�type_�valuer���r�����/builddir/build/BUILDROOT/alt-python310-setuptools-58.3.0-4.el8.x86_64/opt/alt/python310/lib/python3.10/site-packages/setuptools/_vendor/packaging/_typing.pyr���/���s���N)�__doc__�__all__�typingr���r���r���r���r���r����<module>���s����

🔐 Sid Gifari File Manager Pro