o 5i @s:ddlZddlZddlmZddlmZGdddZdS)N)paths_on_pythonpath) namespacesc@seZdZddZddZdS)TestNamespacesc Cst|d}t|d}|d}|d}||f}tjdddt|dt|g}t|t|tjdddt|dt|g}t|tjd d g}tt t|t|Wd d S1sawYd 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.pkgAz 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_packages path_packagestargets install_cmd try_importr_/root/parts/websockify/install/lib/python3.10/site-packages/setuptools/tests/test_namespaces.pytest_mixed_site_and_non_site s>     "z+TestNamespaces.test_mixed_site_and_non_sitecCst|d}|d}tjdddt|dt|g}t|t|tjddg}tt|gtj|t|d Wd d S1sDwYd S) z Installing a namespace packages but also having it in the current working directory, only one version should take precedence. rpackagesrrr r r zimport myns.pkgA)cwdN) rr r rrrrrr)rrrtargetrpkg_resources_imprrr(test_namespace_package_installed_and_cwd4s&  "z7TestNamespaces.test_namespace_package_installed_and_cwdN)__name__ __module__ __qualname__rr$rrrrr s *r)rr setuptools._pathrrrrrrrs