X7ROOT File Manager
Current Path:
/lib/python3.8/site-packages/pip/_internal/utils
lib
/
python3.8
/
site-packages
/
pip
/
_internal
/
utils
/
??
..
??
__init__.py
(0 B)
??
__pycache__
??
appdirs.py
(9.54 KB)
??
compat.py
(9.34 KB)
??
deprecation.py
(3.24 KB)
??
encoding.py
(1.29 KB)
??
filesystem.py
(3.26 KB)
??
filetypes.py
(571 B)
??
glibc.py
(4.29 KB)
??
hashes.py
(3.93 KB)
??
inject_securetransport.py
(810 B)
??
logging.py
(12.73 KB)
??
marker_files.py
(823 B)
??
misc.py
(24.98 KB)
??
models.py
(1.12 KB)
??
packaging.py
(2.96 KB)
??
setuptools_build.py
(1.59 KB)
??
subprocess.py
(9.68 KB)
??
temp_dir.py
(5.39 KB)
??
typing.py
(1.1 KB)
??
ui.py
(13.58 KB)
??
unpacking.py
(9.46 KB)
??
urls.py
(1.45 KB)
??
virtualenv.py
(891 B)
Editing: typing.py
"""For neatly implementing static typing in pip. `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 pip, all static-typing related imports should be guarded as follows: from pip._internal.utils.typing import MYPY_CHECK_RUNNING if MYPY_CHECK_RUNNING: from typing import ... Ref: https://github.com/python/mypy/issues/3216 """ MYPY_CHECK_RUNNING = False
Upload File
Create Folder