📁 File Manager Pro
v10.0.3 | PHP: 8.2.31
Server: LiteSpeed
2026-06-27 19:43:21
📂
/ (Root)
/
opt
/
cloudlinux
/
venv
/
lib
/
python3.11
/
site-packages
/
setuptools
/
tests
/
__pycache__
📍 /opt/cloudlinux/venv/lib/python3.11/site-packages/setuptools/tests/__pycache__
🔄 Refresh
✏️
Editing: test_namespaces.cpython-311.pyc
Read Only
� ,|oi� � �H � d dl Z d dlZd dlmZ ddlmZ G d� d� � ZdS )� N)�paths_on_pythonpath� )� namespacesc �& � e Zd Zd� Zd� Zd� Zd� ZdS )�TestNamespacesc �^ � t j |d� � }t j |d� � }|dz }|dz }||f}t j dddt |� � dt |� � g}t j |� � t j |� � t j dddt |� � dt |� � g}t j |� � t j d d g}t t t |� � � � 5 t j |� � d d d � � d S # 1 swxY w Y d 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) r �build_namespace_package�sys� executable�str� subprocess� check_call� make_site_dirr �map) �self�tmpdir�pkg_A�pkg_B� site_packages� path_packages�targets� install_cmd� try_imports �r/builddir/build/BUILD/cloudlinux-venv-1.0.10/venv/lib/python3.11/site-packages/setuptools/tests/test_namespaces.py� test_mixed_site_and_non_sitez+TestNamespaces.test_mixed_site_and_non_site sx � � �2�6�;�G�G���2�6�;�G�G�� � �0� � � �0� � � �.�� �N� � � � ��J�J� � � � � � � � � �k�*�*�*�� � �/�/�/� �N� � � � ��J�J� � � � � � � � � �k�*�*�*� �N� � 0� � � !��S�'�!2�!2� 3� 3� .� .� � !�*� -� -� -� .� .� .� .� .� .� .� .� .� .� .� .���� .� .� .� .� .� .s � D"�"D&�)D&c �( � t j |d� � }|dz }|� � � t j ddddt |� � t |� � g}t t |� � g� � 5 t j |� � ddd� � n # 1 swxY w Y t j |� � t j dd g}t t |� � g� � 5 t j |� � ddd� � dS # 1 swxY w Y dS ) zc Ensure that a namespace package doesn't break on import of pkg_resources. r �packagesr �pipr r Nr zimport pkg_resources) r r �mkdirr r r r r r r )r r �pkg�targetr r s r! �test_pkg_resources_importz(TestNamespaces.test_pkg_resources_import4 s� � � �0���E�E���*�$��� � ���� �N� � � � � ��K�K� ��H�H� � � !�#�f�+�+� � /� /� /� /� � !�+� .� .� .� /� /� /� /� /� /� /� /� /� /� /���� /� /� /� /�� ��(�(�(� �N� � "� � � !�#�f�+�+� � /� /� .� .� � !�*� -� -� -� .� .� .� .� .� .� .� .� .� .� .� .���� .� .� .� .� .� .s$ �9B�B �!B �%D�D �D c � � t j |d� � }|dz }t j dddt |� � dt |� � g}t j |� � t j |� � t j ddg}t t |� � g� � 5 t j |t |� � � � � d d d � � d S # 1 swxY w Y d S ) z� Installing a namespace packages but also having it in the current working directory, only one version should take precedence. r r$ r r r r r z&import pkg_resources; import myns.pkgA��cwdN� r r r r r r r r r )r r r r( r �pkg_resources_imps r! �(test_namespace_package_installed_and_cwdz7TestNamespaces.test_namespace_package_installed_and_cwdP s2 � � �2�6�;�G�G���*�$�� �N� � � � ��J�J� � ��K�K� � � � �k�*�*�*�� ��(�(�(� �N� � 4� �� !�#�f�+�+� � /� /� E� E� � !�"3��U��� D� D� D� D� E� E� E� E� E� E� E� E� E� E� E� E���� E� E� E� E� E� Es � $C � C�Cc �� � t j |d� � }t j |d� � }|dz }t j dddt |� � dt |� � g}t j |� � t j |� � t j dd g}t t |� � g� � 5 t j |t |� � � � � d d d � � d S # 1 swxY w Y d 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. r r r$ r r r r r z8import pkg_resources; import myns.pkgA; import myns.pkgBr+ Nr- )r r r r r( r r. s r! �5test_packages_in_the_same_namespace_installed_and_cwdzDTestNamespaces.test_packages_in_the_same_namespace_installed_and_cwdm sD � � �2�6�;�G�G���2�6�;�G�G���*�$�� �N� � � � ��J�J� � ��K�K� � � � �k�*�*�*�� ��(�(�(� �N� � F� �� !�#�f�+�+� � /� /� E� E� � !�"3��U��� D� D� D� D� E� E� E� E� E� E� E� E� E� E� E� E���� E� E� E� E� E� Es �1$C"�"C&�)C&N)�__name__� __module__� __qualname__r" r) r/ r1 � � r! r r sY � � � � � �(.� (.� (.�T.� .� .�8E� E� E�: E� E� E� E� Er6 r )r r �setuptools._pathr � r r r5 r6 r! �<module>r9 s� �� � � � � � � � � 0� 0� 0� 0� 0� 0� � � � � � �AE� AE� AE� AE� AE� AE� AE� AE� AE� AEr6
💾 Save Changes
❌ Cancel