/opt/cloudlinux/venv/lib/python3.11/site-packages/numpy/__pycache__/
/opt/cloudlinux/venv/lib/python3.11/site-packages/numpy/__pycache__
NameSizeModeActions
conftest.cpython-311.pyc62140644editdlrm
ctypeslib.cpython-311.pyc215160644editdlrm
dtypes.cpython-311.pyc26510644editdlrm
exceptions.cpython-311.pyc86340644editdlrm
matlib.cpython-311.pyc121450644editdlrm
setup.cpython-311.pyc23080644editdlrm
version.cpython-311.pyc10940644editdlrm
_distributor_init.cpython-311.pyc5650644editdlrm
_globals.cpython-311.pyc41910644editdlrm
_pytesttester.cpython-311.pyc75030644editdlrm
_version.cpython-311.pyc6130644editdlrm
__config__.cpython-311.pyc61340644editdlrm
__init__.cpython-311.pyc166710644editdlrm
Edit: /opt/cloudlinux/venv/lib/python3.11/site-packages/numpy/__pycache__/conftest.cpython-311.pyc (6214B)
krب; \dZddlZddlZddlZddlZddlZddlmZdaiZ ej ej ejdejdddejdddddeej ej ej ed d Zejej erdndd ejd <dZdZdZejdZejdddZejddZ ejddZ!ejddgdZ"dS)z= Pytest configuration and fixtures for the Numpy test suite. N) get_fpu_modez .hypothesisz numpy-profileT)namedeadline print_blobznp.test() profile)rrrdatabase derandomizesuppress_health_checkz..z pytest.ini1NUMPY_EXPERIMENTAL_DTYPE_APIc|dd|dd|dd|dddS)Nmarkersz=valgrind_error: Tests that are known to error under valgrind.z:leaks_references: Tests that are known to leak references.zslow: Tests that are very slow.z,slow_pypy: Tests that are very slow on pypy.)addinivalue_line)configs b/builddir/build/BUILD/cloudlinux-venv-1.0.12/venv/lib64/python3.11/site-packages/numpy/conftest.pypytest_configurer.s IGIII IDFFF I)+++ I688888c8|dddddS)Nz--available-memorystorezSet amount of memory available for running the test suite. This can result to tests requiring especially large amounts of memory to be skipped. Equivalent to setting environment variable NPY_AVAILABLE_MEM. Default: determinedautomatically.)actiondefaulthelp) addoption)parsers rpytest_addoptionr9s5 )'4,.....rc`|jd}||tjd<dSdS)Navailable_memoryNPY_AVAILABLE_MEM)r getoptionosenviron)session available_mems rpytest_sessionstartr#Cs9N,,-?@@M *7 &'''! rcxt}t|adS|tkrt|ft|<|adSdS)z Check FPU precision mode was not changed during test collection. The clumsy way we do it here is mainly necessary because numpy still uses yield tests, which can execute code at test collection time. N)r _old_fpu_mode_collect_results)itemmodes rpytest_itemcollectedr)JsH >>D   "/!6   rfunction)scopeautousec#.Kt}dVt}||kr#td||t|j}|(|\}}td||dS)zC Check FPU precision mode was not changed during the test. Nz@FPU precision mode changed from {0:#x} to {1:#x} during the testzIFPU precision mode changed from {0:#x} to {1:#x} when collecting the test)rAssertionErrorformatr&getnode)requestold_modenew_modecollect_results rcheck_fpu_moder6^s ~~H EEE~~H8006x0J0JLL L&))',77N!+(99?@H:J:JKK K"!r)r,ct|d<dS)Nnp)numpy)doctest_namespaces radd_npr;ss#drc2|dddS)NPYTHONHASHSEED0)setenv) monkeypatchs r env_setuprAws'-----rF)paramsc#Ktj}|jrtjdntjd|jVtj|dS)z Fixture to ensure "legacy" promotion state or change it to use the new weak promotion (plus warning). `old_promotion` should be used as a parameter in the function. weak_and_warnlegacyN)r9_get_promotion_stateparam_set_promotion_state)r2states rweak_promotionrJ|sj  & ( (E}- "?3333 "8,,, - u%%%%%r)#__doc__rtempfile hypothesispytestr9numpy.core._multiarray_testsrr%r& configurationset_hypothesis_home_dirpathjoin gettempdirsettingsregister_profilelist HealthCheckdirname__file__ _pytest_ini load_profileisfiler rrr#hookimplr)fixturer6r;rArJrrras  555555  00GLL$$&& 66 $$ 4D% $$  dTt$z566%gll27??844dLII  w~~k22KOO8K .1 )*888...888&j$///KK0/K($$$...e}%%% & &&% & & &r