U aʹj@s:ddlZddlZddlmZddlmZGdddZdS)N)paths_on_pythonpath) namespacesc@s,eZdZddZddZddZddZd S) TestNamespacesc Cst|d}t|d}|d}|d}||f}tjdddt|dt|g}t|t|tjdddt|dt|g}t|tjd d g}tt t|t|W5QRXd S) z Installing two packages sharing the same namespace, one installed to a site dir and the other installed just to a path on PYTHONPATH should leave the namespace in tact and both packages reachable by import. myns.pkgA myns.pkgBz site-packagesz path-packages-m pip.__main__install-t-cz"import myns.pkgA; import myns.pkgBN) rbuild_namespace_packagesys executablestr subprocess check_call make_site_dirrmap) selftmpdirpkg_Apkg_B site_packagesZ path_packagestargets install_cmd try_importr_/var/www/html/bwave/python/venv/lib/python3.8/site-packages/setuptools/tests/test_namespaces.pytest_mixed_site_and_non_site s<     z+TestNamespaces.test_mixed_site_and_non_sitec Cst|d}|d}|tjddddt|t|g}tt|gt|W5QRXt |tjddg}tt|gt|W5QRXd S) zc Ensure that a namespace package doesn't break on import of pkg_resources. rpackagesrpipr r r zimport pkg_resourcesN) rr mkdirrrrrrrr)rrpkgtargetrrrrrtest_pkg_resources_import4s(   z(TestNamespaces.test_pkg_resources_importc Cst|d}|d}tjdddt|dt|g}t|t|tjddg}tt|gtj|t|d W5QRXd S) z Installing a namespace packages but also having it in the current working directory, only one version should take precedence. rr rr r r r z&import pkg_resources; import myns.pkgAcwdN rr rrrrrrr)rrrr$rpkg_resources_imprrr(test_namespace_package_installed_and_cwdPs$   z7TestNamespaces.test_namespace_package_installed_and_cwdc Cst|d}t|d}|d}tjdddt|dt|g}t|t|tjdd g}tt|gtj|t|d W5QRXd S) z Installing one namespace package and also have another in the same namespace in the current working directory, both of them must be importable. rrr rr r r r z8import pkg_resources; import myns.pkgA; import myns.pkgBr&Nr()rrrrr$rr)rrr5test_packages_in_the_same_namespace_installed_and_cwdms&    zDTestNamespaces.test_packages_in_the_same_namespace_installed_and_cwdN)__name__ __module__ __qualname__rr%r*r+rrrrr s*r)rrZsetuptools._pathrrrrrrrs