o Zh@sdZddlZddlZddlZddlZddlZddlZddlmZddl m Z ddl m Z ddl mZmZdZd Zejd d Zejd d ZGdddZGdddZGdddZdS)z develop testsN)paths_on_pythonpath)develop) Distribution)contexts namespaceszHfrom setuptools import setup setup(name='foo', packages=['foo'], ) z print "foo" c cst4}t}|d||d|dVWdn1s$wYWddSWddS1sr?__doc__rIrMrNr r r r rEbs  rEc@sTeZdZeddZejjee j dddejje dkdddd Zd S) TestNamespacesc Cstjdddt|g}|-tt|g t|Wdn1s&wYWddSWddS1s>wYdS)Nrrz --install-dir)rA executablestrrr subprocess check_call)src_dirrZ develop_cmdr r r install_developts  "zTestNamespaces.install_developZAPPVEYORz-https://github.com/pypa/setuptools/issues/851r4PyPyz.https://github.com/pypa/setuptools/issues/1202cCst|d}t|d}|d}tjdddt|dt|g}t||||t|tjdd g}t t|g t|Wd n1sKwYtjdd g}t t|gt|Wd d S1snwYd S) a Installing two packages sharing the same namespace, one installed naturally using pip or `--single-version-externally-managed` and the other installed using `develop` should leave the namespace in tact and both packages reachable by import. z myns.pkgAz myns.pkgBr&z-mpipinstallz-tz-cz"import myns.pkgA; import myns.pkgBNzimport pkg_resources) rZbuild_namespace_packagerArQrRrSrTrVZ make_site_dirr)r/rZpkg_AZpkg_BrZ install_cmdZ try_importZpkg_resources_impr r r !test_namespace_package_importables8      "z0TestNamespaces.test_namespace_package_importableN)r=r>r? staticmethodrVr)rDZskipifboolosenvirongetplatformpython_implementationrZr r r r rPss   rP)rOr]r6r`rSrAr)Zsetuptools._pathrZsetuptools.command.developrZsetuptools.distrrrrrZfixturerr r!rErPr r r r s(     ,