Ji @SSKrSSKrSSKJr SSKJr "SS5rg)N)paths_on_pythonpath) namespacesc \rSrSrSrSrSrg)TestNamespaces c Z[R"US5n[R"US5nUS- nUS- nXE4n[RSSS[ U5S[ U5/n[ R "U5 [R"U5 [RSSS[ U5S[ U5/n[ R "U5 [RS S /n[[[U55 [ R "U5 S S S 5 g !,(df  g =f) 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_imports b/var/www/html/dynamic-report/venv/lib/python3.13/site-packages/setuptools/tests/test_namespaces.pytest_mixed_site_and_non_site+TestNamespaces.test_mixed_site_and_non_site s226;G226;G0 0 . NN    J     k*  / NN    J     k* NN  0 !S'!2 3  ! !* -4 3 3s <D D*c [R"US5nUS- n[RSSS[ U5S[ U5/n[ R "U5 [R"U5 [RSS/n[[ U5/5 [ R "U[ U5S 9 S S S 5 g !,(df  g =f) z Installing a namespace packages but also having it in the current working directory, only one version should take precedence. r packagesr r r rrzimport myns.pkgA)cwdN) rrrrrrrrr)rrrtargetrpkg_resources_imps r!(test_namespace_package_installed_and_cwd7TestNamespaces.test_namespace_package_installed_and_cwd4s 226;G*$ NN    J  K  k*  ( NN    !#f+ /  ! !"3U D0 / /s C CN)__name__ __module__ __qualname____firstlineno__r"r)__static_attributes__r+r!rr s(.TEr1r)rrsetuptools._pathrrrr+r1r!r4s 0FEFEr1