o j@slddlmZddlZddlZddlZddlZeeZe dZ dddZ dd d Z dd d Z dd dZdS)) annotationsNz8include-system-site-packages\s*=\s*(?Ptrue|false)returnboolcCstjttdtjkS)znChecks if sys.base_prefix and sys.prefix match. This handles PEP 405 compliant virtual environments. base_prefix)sysprefixgetattrr r \/var/www/html/django_cbt/venv/lib/python3.10/site-packages/pip/_internal/utils/virtualenv.pyrunning_under_virtualenvsr list[str] | NonecCsftjtjd}z t|dd}|WdWS1s!wYWdSty2YdSw)zReads {sys.prefix}/pyvenv.cfg and returns its contents as list of lines Returns None, if it could not read/access the file. z pyvenv.cfgzutf-8)encodingN) ospathjoinrropenread splitlinesOSError)pyvenv_cfg_filefr r r _get_pyvenv_cfg_liness ( rcCsPt}|durtddS|D]}t|}|dur%|ddkr%dSqdS)aZCheck `{sys.prefix}/pyvenv.cfg` for system site-packages inclusion PEP 405 specifies that when system site-packages are not supposed to be visible from a virtual environment, `pyvenv.cfg` must contain the following line: include-system-site-packages = false Additionally, log a warning if accessing the file fails. NzCould not access 'pyvenv.cfg' despite a virtual environment being active. Assuming global site-packages is not accessible in this environment.TvaluefalseF)rloggerwarning#_INCLUDE_SYSTEM_SITE_PACKAGES_REGEXmatchgroup) cfg_lineslinerr r r _no_global_under_venv%s  r!cCstrtSdS)zHReturns a boolean, whether running in venv with no system site-packages.F)r r!r r r r virtualenv_no_globalBsr")rr)rr ) __future__rloggingrrer getLogger__name__rcompilerr rr!r"r r r r s