| Server IP : 121.121.20.254 / Your IP : 216.73.216.202 Web Server : Microsoft-IIS/10.0 System : Windows NT WEB-SERVER 10.0 build 20348 (Windows Server 2022) AMD64 User : IUSR ( 0) PHP Version : 8.3.28 Disable Function : NONE MySQL : ON | cURL : ON | WGET : OFF | Perl : OFF | Python : OFF | Sudo : OFF | Pkexec : OFF Directory : C:/Python315/Lib/test/test_importlib/source/__pycache__/ |
Upload File : |
R
>lqj� c �f � ] QH GsGs \O Q2 s] PHs] PHs] PHs] PH s] PH$s ] PH(s
] QH,Gs ] PH4s
Q Q\O 2 s Q Q\2 s\O \\Q5 v ss Q Q
\2 s\O \\Q5 v ss\Q6X c \
O. 2 P! P! )� )�abc�utilzimportlib.machinery)�make_legacy_pycc �� ` � \ sQ s]s n QsQ sQ sQQPQP-Q kksQ sQ s Q s
Q
sQ sQ s
Q
sQ sQ s\O$ \O( Q6g Q2 Q 2 sQ sQsU sP! )�FinderTestsa For a top-level module, it should just be found directly in the
directory being searched. This is true for a directory with source
[top-level source], bytecode [top-level bc], or both [top-level both].
There is also the possibility that it is a package [top-level package], in
which case there will be a directory with the module name and an
__init__.py file. If there is a directory without an __init__.py an
ImportWarning is returned [empty dir].
For sub-modules and sub-packages, the same happens as above but only use
the tail end of the name [sub module] [sub package] [sub empty].
When there is a conflict between a package and module having the same name
in the same directory, the package wins out [package over module]. This is
so that imports of modules within the package can occur rather than trigger
an import error.
When there is a package and module with the same name, always pick the
package over the module [package over module]. This is so that imports from
the package have the possibility of succeeding.
c �� � U O O U O O 1U O O U O O 1,oU O O
U,UN3 ! �N)� machinery�SourceFileLoader�SOURCE_SUFFIXES�SourcelessFileLoader�BYTECODE_SUFFIXES�
FileFinder)�self�root�loader_detailss && �;C:\Python315\\Lib\test\test_importlib\source\test_finder.py�
get_finder�FinderTests.get_finder'